Geeks With Blogs

Disclaimer: The views expressed on this blog are my own and do not necessarily reflect the views of my employer.

Creative Commons License

Check out my profile!

INETA Community Speakers Program

Follow enriquelima on Twitter
Locations of visitors to this page

Intentional Thinking Enrique Lima

I have used Source Control since the first release, and even then it was a great option for bringing source control for the DB.  Well a great tool just got better and better rounded in the process.

Again, the integration with multiple repositories like SVN or in my case TFS is great.  What makes it even better is the near zero interaction a DBA would have to have with Visual Studio in order to drive the solution from managing a few stored procedures or tables to driving a database change management process.

The focus, of course, is to deliver a solution that allows you to develop a solution.  Yes, I did say develop.  This is intended to serve the results it needs when we establish a process to move from Dev to QA to Prod.  Assisting in establishing baselines and the call for release points.

Let’s start from the process of enrolling your database to be under Source Control.  What is needed?  a source control repository, and the path to where, within that repository, you will be storing the scripts and change records.  This is where the work starts, obviously, you will do an initial baseline entry as your objects get created.  This is specially true if you already have a database you will work with, and now you are tracking progress and changes for it.  If you are used to the process of checking in your changes and checking out the items to change, well this should be no different.

As you work with the changes, you will determine when your changes or work reaches the maturity or desired point for the solution to move from Dev to QA.  Here is where there are differences from the previous version of the product.  How do we make this happen?  We establish baselines, then we take those baselines and migrate them to the desired server.  This makes use of Schema Compare where you can generate a change record or use the script that was generated from Source Control.

In my lab and testing process I have been using TFS 11, Visual Studio 11 and SQL Server 2008 R2.  I am waiting for compatibility with SQL Server 2012, but I am guessing that will not be too far down the road.

It has been a busy time, but the intention is to have a step by step process of a scenario that makes use of the items talked about above.

But, so far, great changes and additions to an already great product.

Posted on Sunday, April 22, 2012 10:27 PM SQL Server , Reviews | Back to top

Comments on this post: Source Control from red gate software summary review

# SSMS 2008 support
Requesting Gravatar...
SQL Source Control now supports SQL Server Management Studio 2008. Visit Help/Check for Updates from the SQL Source Control window.

Looking forward to the step-by-step scenarios!
Left by David Atkinson on Apr 23, 2012 4:07 AM

comments powered by Disqus

Copyright © Enrique Lima | Powered by: