TSQL Version Control
-
Our development team has recently expanded and we are now at the point where it is becoming difficult to manage changes to code and objects in our database.
We're a .NET development shop and are using Visual Source Safe (not the best option, I know, but it's what we've got and I don't get to be the one who decides to switch). Our Presentation and Middle tiers are served fairly well by it but as we all know, there's no facility within Visual Studio for integrating VSS with our SQL Server code.
My question is, How have other shops dealt with the same problem? Does anyone have any suggestions, workarounds or third-party solutions that have worked well? I really don't know how to go about evaluating competing solutions, and most of my internet searches just come up with commercial web sites with marketing material focused on what they want to sell. Any help, advice and/or anecdotes will be greatly appreciated.
-
All it really requires, IMO, is a bit of discipline.
Script every object from your database and check it into VSS.
Any time you need to change an object, check out and edit the script, then apply the change and check back in the script. Ban developers from using Enterprise Manager.
It's a bit of a change at first, but once you get used to it, it will be second nature.
--
Adam Machanic
whoisactive -
The old SQL source control problem....
I agree discipline should be the best way, but developers are developers (and worse, development managers are development managers :whistling
, and the app has to go tonight, and the stored procedures not working, and I'm in query analyser, so I'll just quickly change it...Depending on your needs from SourceSafe, I like Bill Wunder's utility which scripts the DDL to sourcesafe each night. That way we can use whichever tool to edit SQL, and know that at least we have the last copy in sourcesafe. But this won't work if you are trying to track who made a change.
And I personally really like VSS and Visual Studio.Net working together...
Steve
-
hey,
Just wanted to let you guys know that this 'old SQL source control problem' has been solved. there is a tool that does just that:
-
..as SDoughty says..certainly easier said than done...I've been using the "discipline method" for the last three years and I'm still waiting for it to become second nature...
Shall check out Yonision's link first chance I get...
**ASCII stupid question, get a stupid ANSI !!!** -
Yes...discipline and a "big stick". We've been using VSS for version control of all DDL and sql code for a while now. Periodically our Audit Team does a comparison of what is in production and what is in VSS. A while back we let 2 dbas go for not following source control procedures. Things have been "tighter" since. At any rate, I hear eclipse has some tools for SQL Server source control integration with cvs..but I've never played around with it.
Mathew J Kulangara
sqladventures.blogspot.com
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply