Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Source control for databases Expand / Collapse
Have you considered using source control for databases?
Poll ResultsVotes
No
 
7.14%
4
We evaluated it and couldn't come up with a productive method
 
16.07%
9
We tried it and abandoned it
 
3.57%
2
Yes we are evaluating it
 
44.64%
25
Yes we source control our databases
 
28.57%
16
Member Votes: 54, Anonymous Votes: 0. You don't have permission to vote within this poll.
Author
Message
Posted Wednesday, July 15, 2009 9:02 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 1:34 AM
Points: 2,904, Visits: 1,822
Every now and again the subject of source-controlling database objects gets raised.

I work in a 400 strong IT department and so far the only situation we have had where code clashes occurred were in an apallingly badly designed database. Had the database been designed properly there would have been no clash.

I am curious to know what your experience with database source control has been.


LinkedIn Profile
Newbie on www.simple-talk.com
Post #753558
Posted Wednesday, July 15, 2009 10:10 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 13,872, Visits: 9,596
I use source control for all DDL commands to be issued. Haven't found that it actually helps with anything, but it might some day. I think it makes the other devs and such feel more comfortable, gives them a sort of warm fuzzy feeling that they are "doing it right".

I'm a firm believer in what could be called "service packs" for the database. All DDL scripts and any related DML scripts (to populate lookup tables and such) get put into a single script that contains error handling, commenting, lists the author(s) and the purpose of the changes, and can be run repeatedly without harming the database or crashing the script. If stored and run sequentially, starting with the original "create database" script, they should return a database to any point-in-time you want, in terms of code and structure (not data, of course).

Storing those in Source Safe makes the devs comfortable. And, since they need to be kept somewhere, it might as well be in a source control system.

That's what I use source control for. Could just as easily store the scripts as varchar(max) objects in a database. Doesn't matter much to me.


- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #753640
Posted Wednesday, July 15, 2009 10:45 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:38 PM
Points: 31,018, Visits: 15,453
The only good method I've seen so far is to source control the DDL scripts (maybe DML deployment as well).

As soon as you allow GUI changes, things easily get out of hand.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #753667
Posted Wednesday, July 15, 2009 11:12 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:38 AM
Points: 13,755, Visits: 28,147
I love it. Integrating our builds with the development builds makes everything so much easier. The power that comes from knowing exactly what has changed, when, by whom, makes all our development and deployment processes work better. The tool that really makes it all shine is Visual Studio Team System Database Edition, aka Data Dude. Great stuff.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #753680
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse