Comments
Sort by recent activity
Yes. The minor changes were committed before I attempted the "Get Latest".
We have 7 copies of the same database (production, build, developers). They are all set up in SSC as Dedicated and they all point to the same TFS projects for database and migration scripts. These 7 database should all be at the same version right now. However, I see 3 different values for SQLSourceControl Database Revision under the Extended Properties.
Thanks / comments
Yes. The minor changes were committed before I attempted the "Get Latest".
We have 7 copies of the same database (production, build, developers). They are all set up in SSC as Dedicated and they ...
You are correct. I went back and looked at the project history. I never noticed that it was creating 2 changesets for each commit with a migration script.
The migration scripts are not getting picked up, though, when we do get latest. This has just started happening. The databases all share the same scripts and migrations folder in TFS.
Thanks / comments
You are correct. I went back and looked at the project history. I never noticed that it was creating 2 changesets for each commit with a migration script.
The migration scripts are not getting pi...
Here's an update on the migration scripts. I made some changes to the database this weekend. I started in my development copy. These changes were very minor - added 2 columns to end of an existing table - and so they were not committed with a migration script. When it came to to update the second database, rather than seeing the changes (2 new columns), the Get Latest screen presented the last 2 migration scripts that where checked in, even though those changes had already been applied to the second database.
This would appear to be a bug in SSC. / comments
Here's an update on the migration scripts. I made some changes to the database this weekend. I started in my development copy. These changes were very minor - added 2 columns to end of an existi...