August 23, 2010 at 3:16 am
Hello,
our company stores most of it's business logic in SQL Server stored procedures. As the number of employees grows, we are wondering how we can implement a CVS for our stored procedures so 2 developers don't work on the same procedure at the same time, etc.
We would prefer working with something directly from sql server management studio.
Any ideas?
Thanks.
August 23, 2010 at 3:37 pm
Did you check out SQL Source Control from Redgate? (Note: I haven't used it; I've just seen it advertised a bit lately...)
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 23, 2010 at 11:36 pm
That's a nice tool, however, quite expensive for our tastes...
September 3, 2010 at 12:13 pm
If your developers don't have the right to install the updates on the DB then there is no problem (co create_sp.sql, make changes, ci, tag, email DBA and ask him to update the sp using the tag).
If your developers do have the right to install the updates on the DB there there will be problems 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply