Support Getting Latest Migration Scripts
According to Red Gate support, migration scripts only run when using SQL Compare, not when using Get Latest within SQL Source Control. Therefore if I have data, real or test, in every development instance, the Get Latest tab is useless in the product and I must use SQL Compare to deploy the changes. I can't imagine it would be too difficult to just run the migration script when using Get Latest.
Nick
shared this idea
Migration scripts are used in SQL Source Control when Getting Latest. Once you click on the “Get Latest” button, you should recieve a warning about the migration script. If it fails, there will be an option to edit the script it was trying to run. The best thing to do is review the script and execute it in SSMS. If there’s an error, it may be a syntax error within the migration script. Once it is corrected, you can execute the script, then refresh the Get Latest tab and you should be in synch.
I’m sorry about the confusion.
-
Nick
commented
I checked in a migration script and when I used get latest from another, I received an error regarding something that was covered in the migration script. I tinkered with it a bit, called Red Gate support, and was told SQL Source Control does not support migration scripts when using Get Latest. I was told that Migration Scripts are only used for deploying through SQL Compare and that's what I should be using any time I'm deploying changes to any instance where data lose might occur.
If you're saying it is supported, than it's probably something I'm doing wrong which is why I called support. Unfortunately, I was turned away.
-
Migration scripts *are* used for get latest. You should get a warning dialog when these are picked up. Have you tried this and failed to get it working?
