What is the process for automating commits

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

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace, andy.campbell.smith

What is the process for automating commits

Postby lazytrbar » Thu Jan 24, 2013 11:16 pm

I'm just getting started using RedGate source control. My question is this. Is there a way to automate (for example nightly) the commit process.

Our goal here is that we have a lot of programmers working on the dev box and we would like a history of their changes and a quick way to use those scripts to build another database remotely (offline) at any given time.
lazytrbar
 
Posts: 2
Joined: Thu Jan 24, 2013 11:03 pm

Postby Anu Deshpande » Mon Jan 28, 2013 10:09 am

Thanks for your post.

Normally the actions carried out by SQL Source control would be performed manually by each developer when they're happy with the work they have completed and are ready to commit the changes to the source control repository. It's probably not a great idea to have check-ins performed automatically, as a developer might have left the database in an inconsistent state.

If you want to automate the deployment of these checked-in changes to other environments, such as a staging or test environment, the best thing to use would be SQL Compare. You can automate the process using the command line interface.

Here is an article that discusses the workflow. Click here

I hope this helps.
Anuradha Deshpande
Product Support
Redgate Software Ltd.
E-mail: support@red-gate.com
Anu Deshpande
 
Posts: 692
Joined: Mon Apr 20, 2009 3:53 pm
Location: Cambridge


Return to SQL Source Control 3

Who is online

Users browsing this forum: No registered users and 1 guest