Posts
245
Trackbacks
0
April 2012 Entries
Presentation on SQL Server Health in a SharePoint environment
Posted On Sunday, April 22, 2012 10:34 PM | Comments (0)
Source Control from red gate software summary review

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 | Comments (1)
Database Development and Source Control

I have been working with Database Development and the aspects that come with it, the pain and the joy of moving from Dev to QA and then on to Production.  Source Control has a place in Dev, and that is where the baselines should be established.

Where am I going with this? I have been working with Redgate’s Source Control 3.0, and I am seeing some features that are great for the process of moving from Dev to … well something that allows for quite a level of control.  We are not only talking about scripting the structure of a database, but creating a baseline, working with migration scripts, and integrated with Redgate’s Schema Compare. 

There is a detailed paper that will be posted here in the next day or so to provide step by step information of the process to define your baseline in Dev and then take it to the desired destination.

In the meantime, check the Webinars Redgate has regarding this process and products.

Posted On Thursday, April 5, 2012 7:38 AM | Comments (0)
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 about.me profile!

INETA Community Speakers Program

Follow enriquelima on Twitter
Locations of visitors to this page