April 14, 2008 at 9:24 am
Hi, I'm looking for assistance/advice in the areas of source control and change mgmt. We are a small shop (4 developers and one DBA). We would like to implement a change mgmt process for check-in/check-out of Db objects (incl SSIS packages) between our DEV/TEST/PROD environments. We have a modest number of PRODUCTION databases and objects to support so price and appropriate scale are significant factors. I would very much appreciate tool and best practice recommendations/suggestions.
TIA, Chris.
April 16, 2008 at 11:10 am
there are several FREE source-code control systems available (eg subversion)
and this specifically for SS2005 objects using VSS
http://www.codeplex.com/SqlSource
also view these concerning VSS
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=365068&SiteID=1
http://blogs.msdn.com/richardb/archive/tags/vss/default.aspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=146183&SiteID=1
apart from the VS200x solutions there is also a little-known genre within SS2005
- suggest you try SSMS View SolutionExplorer
http://msdn2.microsoft.com/en-us/library/ms173570.aspx
HTH
Dick
April 17, 2008 at 1:21 pm
Yes, it does help. Thanks for the response.
April 18, 2008 at 12:38 am
For SQL Server, MS has come up with integrated source control in SQL Server 2008.......I think it is time to upgrade.....:)
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
April 18, 2008 at 12:59 am
chandrachurhghosh (4/18/2008)
For SQL Server, MS has come up with integrated source control in SQL Server 2008.......I think it is time to upgrade.....:)
I wasn't sure that anything had changed between 2005 and 2008 as far as source control for SQL Server 2008. What's new? As far as I can tell "integrated" means that its integrated with Visual Source Safe. Problem is that Visual Source Safe isn't integrated with SQL Server so it can't tell you if an object has changed outside of source control.
April 18, 2008 at 1:46 am
Well, database evolution is sort of at the center of my interest, and I've been working on such a solution. On http://www.simple-talk.com/sql/database-administration/source-control-and-databases/ I describe some of the problems you are most likely to run across when setting up source control for databases. I do not talk much about the tools in that article. One choice is Microsoft's Visual Studio For Team Systems for Database Professionals; if you can afford it, it is worth exploring its features. DBGhost is another possible solution. The one I worked on is Red Gate's SQL Compare (http://www.red-gate.com/products/SQL_Compare/index.htm). It can work with many source control systems, but most importantly it can script your database, and synchronize the schema of your database (it can update both the live db based on changes to the creation scripts, and the other way around, it can update the SQL creation scripts based on changes to the live database). These creation scripts form the bridge between a database schemata and source control 🙂
Regards,
Andras
April 18, 2008 at 2:29 am
Andras Belokosztolszki (4/18/2008)
Well, database evolution is sort of at the center of my interest, and I've been working on such a solution. On http://www.simple-talk.com/sql/database-administration/source-control-and-databases/ I describe some of the problems you are most likely to run across when setting up source control for databases. I do not talk much about the tools in that article. One choice is Microsoft's Visual Studio For Team Systems for Database Professionals; if you can afford it, it is worth exploring its features. DBGhost is another possible solution. The one I worked on is Red Gate's SQL Compare (http://www.red-gate.com/products/SQL_Compare/index.htm). It can work with many source control systems, but most importantly it can script your database, and synchronize the schema of your database (it can update both the live db based on changes to the creation scripts, and the other way around, it can update the SQL creation scripts based on changes to the live database). These creation scripts form the bridge between a database schemata and source control 🙂Regards,
Andras
Hey Andras. Database evolution has been the center of my interest for the last 3 years too. And likewise I've been working on my own solution (http://www.sqldbcontrol.com/beta.aspx). Don't worry, there's no chance it can compete with you guys. Besides, there's only so much one person can do in their spare time. But I do think my Intellisense is better than yours 😉 - even if it doesn't integrate into SSMS or VS :(.
In my case I wanted a solution that minimized the need for developers to seperately (and independantly) manage source control. In other words, when I check in an object I want those checked-in changes to be immediately applied to the database. Likewise when I rollback an object I want the rolled-back changes to be immediately applied to the database.
I actually went to one of your talks, which mirrors the content you have on http://www.simple-talk.com so thanks for the link, that will prove useful. I've been using SQLCompare 5 for a while so I ought to check out the latest version and see what's changed.
April 18, 2008 at 3:01 am
Hi Karl,
I must admit I have not looked at your solution yet (hence not including it in my response), but I'm looking forward to playing with it for a while. The more solutions there are to support source control for databases, the better it is for larger database projects. While everyone says that they want source control for their databases, this is still a task that gets constantly postponed 🙂
Regards,
Andras
April 18, 2008 at 3:20 am
check out the following link -
http://www.sqlservercentral.com/articles/Development/2743/
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
April 18, 2008 at 3:44 am
You can also check-out the following links -
http://sql-server-version-control.qarchive.org/
http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1093178,00.html (nice one)
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
April 18, 2008 at 3:52 am
chandrachurhghosh (4/18/2008)
check out the following link -
That relates to SQL Server 2005. But as I stated, that only integrates SSMS with Visual Source Safe but not vice versa. In my opinion this isn't a good source control solution, which the author himself concedes in the conclusion, saying:
"...So, whenever the database structure is modified or a script has been updated, the only way to reflect the changes in the source control is to script the file and update the changes. Use of source control feature for database objects is not relevant till it is based on actual objects. A feature, which can be incorporated in future releases of SQL Server. "
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply