Comments
Sort by recent activity
O.k. I will start with a clean slate and retry the scenario from scratch when I get a chance. I'll post the results once I'm finished. / comments
O.k. I will start with a clean slate and retry the scenario from scratch when I get a chance. I'll post the results once I'm finished.
Thank you, Brian. The patch you sent me (SQL Compare Pro v10.0.0.162) did resolve the issue I was experiencing. The migration scripts are now being included when I generate a deployment script using source control versions for both the source and target. / comments
Thank you, Brian. The patch you sent me (SQL Compare Pro v10.0.0.162) did resolve the issue I was experiencing. The migration scripts are now being included when I generate a deployment script us...
Thank you for the reply. I verified that both the migration script (.sql) and the .migrationScript files are checked into SourceGear Vault. I don’t believe this is a source control issue because both my first test and my second test were performed using the “Latest (Head)†version out of Vault as the Source. Also, in both tests, the SQL Compare tool indicated visually that it would be using the migration script and SQL Compare allowed me to view the migration script. The issue is that under my first test SQL Compare actually included the migration script in the generated deployment script, and in the second scenario it skipped using the migration script when generating the deployment script (even though it had visually indicated it would use it). The only difference I can discern is that my first test used a SQL Server database as the Target and the second test used a source controlled version as the Target.
Please clarify what you meant by “I’ve had a look into reproducing.†Does that mean you tested the scenario and that SQL Compare actually used the migration scripts when generating a deployment script to go from one source control version to another? / comments
Thank you for the reply. I verified that both the migration script (.sql) and the .migrationScript files are checked into SourceGear Vault. I don’t believe this is a source control issue becaus...