Hey everyone,
Our teams here have always been frustrated by the 5 to 20 minute wait times for the commit tab on SQL Source Control so I decided to check out SQL Change Automation. It appears to be much faster (running at about 1-3 minutes for our largest db).
My question is how do I migrate over to it without losing our commit history? Is there an easy way to import it or folder structure change that I can do in the existing repository so that we can keep our history?
Comments
3 comments
-
Hi @JMcKinnon
Unfortunately, we don't have a way to support migrating the commit history from SQL Source Control to SQL Change Automation. -
@Diogo Is there a way I can change the folder structure of SQL Source Control to move towards SQL Change Automation? I can keep the commit history if I do a new commit that just moves the files into the new structure but I need to know if the scripts generated from each are compatible (same format, tool will recognize, etc.)
-
The scripts that SQL Change Automation holds in the Offline Schema Model folder should be compatible but the ones in the Programmable Objects folder wouldn't be compatible because they also have DROP statements at the beginning.
A bit more information in our documentation
https://documentation.red-gate.com/display/SCA3/Programmable+Objects
https://documentation.red-gate.com/display/SCA3/Offline+Schema+Model
Add comment
Please sign in to leave a comment.