Deploy static table data best practice

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Deploy static table data best practice

Postby greg.strauss » Wed Oct 17, 2012 10:24 pm

What is the best practice for deploying static table updates from Source Control to a staging or production server?

Currently, we update the static tables on our dedicated development system and check them in successfully with SSC (we use SVN) . We now want to deploy these changes from source control to a staging server that already exists for our QA department

So, if I use SQL Data Compare and use Source Control as the source and the staging server as target, the SQL data comparison tool (by default) will try to compare all tables. Is there a way to tell SQL Data Compare to only select the statically linked tables in Source Control? I'm not sure why you'd ever want to do a full data comparison when the source is Source Control.

Also, is there a way to unify the deployment step so that both schema and data changes (in statically linked tables) can be deployed in one go? Now we have to remember to do both (SQL Compare and SQL Data Compare) for a deployment.
Posts: 4
Joined: Wed Oct 17, 2012 10:10 pm
Location: Victoria, BC

Postby stanori » Mon Oct 22, 2012 11:49 pm

Hi gregg.strauss,

Thanks for your forumn post. In regards to your question about deploying static tables, you would typically use SQL Data Compare to deploy the changes.

In the latest build of SQL Compare ( there is a new command line switch "/include:static" which can be used to deploy static data from SQL Source Control to your target database.

Best Regards,
Steve Tanori
Product Support
Red Gate Software Ltd.
Posts: 84
Joined: Mon Apr 23, 2012 12:13 pm

Postby greg.strauss » Thu Oct 25, 2012 2:58 pm

thx for the reply.

In SQL Compare, is there a UI equivalent to "/include:static"? In other words, can I trigger this option in the user interface someplace? I don't see this option in the "Options" tab in SQL Compare (I have

To do a deployment, we initiate it from SSMS, so generally we are isolated from the command line.

I would suggest having this option on the "Data Sources" tab when you select "Source Control" as the Source.
Posts: 4
Joined: Wed Oct 17, 2012 10:10 pm
Location: Victoria, BC

Return to SQL Source Control 3

Who is online

Users browsing this forum: No registered users and 0 guests