Comments
Sort by recent activity
Ok, just to clarify my meaning:
In link static data in SSMS / SQL Src Control, it doesn't give the option to specify the fields to use for the comparison key, and just uses any PK defined in the db itself.
In SQL Data Compare itself it gives the option to specify the fields.
In my particular case there is a PK used for update and delete operations, but the real unique compound keys are 3 string fields.
Is there any way I can get SSC to use these :?: / comments
Ok, just to clarify my meaning:
In link static data in SSMS / SQL Src Control, it doesn't give the option to specify the fields to use for the comparison key, and just uses any PK defined in the db...
The article with detail of the shared model limitations is useful, especially as it hints at your use of a local copy of the scripts (on each dev pc, even in shared db mode) to determine changes and conflicts. / comments
The article with detail of the shared model limitations is useful, especially as it hints at your use of a local copy of the scripts (on each dev pc, even in shared db mode) to determine changes an...
SSC is stating that one of the differences is a conflict.
I'd like tounderstand how SSC can determine this if we are using a shared db model? / comments
SSC is stating that one of the differences is a conflict.
I'd like tounderstand how SSC can determine this if we are using a shared db model?
A typical scenario I have just had along these lines, is that I have changed a column type and name, but the new column data is initially generated from that of the old column. so steps must be:
- create new column
- run update script to populate new column
- drop old column
this is fairly typical I imagine, but I'm concerned that SQL Source Control wont be able to help me with this, or indeed SQL Compare
Idea:
perhaps every checkin could have an optional associated data modification script, tho in this case I'd still have to do this change in 2 seperate checkins, so its not ideal at all.
I'm prepared to write custom SQL, but its how this can be integerated in and performed as part of the deployment script.
if the checkin contained the deletion of the old column, and the addition of the new one, then SSC would allow me to add a data migration script to the checkin. I'd still have to communicate to SSC the relationship between these columns, and when to run th script. / comments
A typical scenario I have just had along these lines, is that I have changed a column type and name, but the new column data is initially generated from that of the old column. so steps must be:
-...
some pre and post change sql script might be a way of handling these data migration challenges. it would only work if the addition of new tables/columns was done as one change, the data migration script done as a change after that, and the drop of the old tables/columns done after that.
Just need to be able to insert a change in to SSC that is a manual data migration script, to be run after a particular version is deployed.
simple example:
Changeset4: add new column B to table X
C5: drop column A
associate UPDATE Script with Changeset4, eg:
UPDATE X SET B = A +1 / comments
some pre and post change sql script might be a way of handling these data migration challenges. it would only work if the addition of new tables/columns was done as one change, the data migration ...