October 25, 2002 at 9:54 am
I am trying to maintain SQL-Server scripts for SQL-Server 2000 into VSS. The basic reason is to maintain history and not to allow 2 developers to work at the same time. I added all the scripts to VSS. I am not sure how to configure the developers to use this database for creating their stored procedures etc and make it talk with SQL- Server and test it in developers machines.
Thanks in Advance
Madhavan
Madhavan
October 25, 2002 at 10:11 am
I wrote some information on this in http://qa.sqlservercentral.com/columnists/sjones/vcspart1.asp. You need to get people in the habit of "checking" out the files and then editing them from the file, not the server. That is the only way to handle this until QA or EM get some VSS integration.
Steve Jones
http://qa.sqlservercentral.com/columnists/sjones
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
October 28, 2002 at 10:11 am
We have worked out a solution for this that is a bit of a hack. We have created a VB executable that is scheduled to run every 30 minutes - it checks out everything, scripts everything, and checks everything back in. Because VSS doesn't check in unchanged files (it's a setting in VSS), we end up with reasonably effective version control. We just don't know who made the changes and some fast changes are lost.
Russell Sinclair
Author "From Access to SQL Server"
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply