Migration workflow

[bhopenw]

Just wondering if there are going to be built in region/environment migration tools or will have to leverage SQL Compare and Data Compare?

Thus far the TFVC integration seems great, but I having trouble seeing how we can leverage this to improve our DB migrations from region to region (DEV, TST, PRE, PRD).

Thanks,

BJHop

[David Atkinson]

The SQL Source Control add-in's role is to allow you to easily commit and retrieve changed to and from source control. For the deployment/synchronization side you have to use SQL Compare / SQL Data Compare. In a future version these tools will be integrated much tighter together so you won't need to leave SSMS to achieve this. We eventually plan to allow the management of versions from within SSMS, such as tagging/labelling and getting these 'versions' from source control.

David Atkinson
Product Manager
Red Gate Software

[bhopenw]

Okay

Question:
Will SQL Compare be able to view this source as a Scripts Folder? I see a RedGate.scc file where with SQLCompre/SQLChangeSet its RedGateDatabaseInfo.xml.

Meaning, can I call SQL Compare from the cmd line after the source has been downloaded to a local workspace?

thanks,

BJHop

[David Atkinson]

Yes. The RedGateDatabaseInfo.xml file is also used by SQL Source Control. You will be able to 'get' this from source control to a folder and load this up the source data source in SQL Compare Pro. And yes this works with SQL Compare's command line.

In fact you should be able to prove this to yourself if you've installed the early access build. If it doesn't work, please let us know.

In a later version, we'll let you deploy any source controlled version of a database straight from SSMS. In the interim the workaround is to get it manually from source control to a folder and load it into SQL Compare. It's a couple of additional steps, but it's still pretty simple.

David