How can we help you today? How can we help you today?
element533
Activity overview Badges (0) Posts (2) Comments (2)

Comments

Sort by recent activity
Hi David, Thanks for your response. David Atkinson wrote: Can I ask why you need these custom scripts to be 'accounted for' in your versioning process? Is there any reason why you can't generate the script with SQL Compare and simply hand-modify the script to your liking before saving it off? That would certainly be an acceptable solution, but where does that leave us in regards to source/version management? For example, if Developer A writes such a custom script, executes it against his working database, and commits the schema to source control using SQL Source, and then Developer B updates his working database using SQL Source, what happens? Unless SQL Source "knows" that the custom script is required when updating from rev X to rev Y, it will just send down some drop column and create table statements and be done with it, correct? That would blow away Dev B's address data, plus it would fail if there were a NOT NULL foreign key constraint on AddressId (because there would be no rows in the Addresses table). Does Dev A have to check in the custom script by hand? If so, where? How does that get communicated to Dev B? How does it get communicated to Dev C who isn't sure what version of the database he already has? We want a system or tool that can help manage these questions for us, so we can spend our time engineering the data model instead of engineering change control processes. This is not merely a development issue. It also concerns production releases. If we have to manually manage a library of custom scripts and manually ensure that they are executed in the right order and only once, the benefit of using SQL Source to manage our schema starts to fall away. We end up having to still do what we do today (check in custom scripts and manage their deployment by hand). We are comfortable *writing* scripts by hand, but we are really looking for help in terms of managing and versioning them in the context of the DB schema as a whole. Schema versioning sometimes includes orchestrated or strategically designed DML and data migration steps; it is not simply a point-to-point diff of structures, relationships, and constraints. Does that make sense? I know I'm probably preaching to the choir here... [image] What features are coming in the new versions of your products that you think address this? Thanks, Steven / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Normalizing a table into two tables while preserving data
Hi David, Thanks for your response. David Atkinson wrote: Can I ask why you need these custom scripts to be 'accounted for' in your versioning process? Is there any reason why you can't generate t...
0 votes
That sounds exactly like something that would help with this scenario... That is the new feature that's supported in the upcoming version of the tools? / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Normalizing a table into two tables while preserving data
That sounds exactly like something that would help with this scenario... That is the new feature that's supported in the upcoming version of the tools?
0 votes
Total activity
5
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1