Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tc101
Starting Member
4 Posts |
 Posted - 2008-11-10 : 17:50:28
|
| Is there a good tool to keep track of the changes made by several programmers to the tables, stored procedures and so on in SS 2005? Several of us are working at home and accessing it over the internet with SS Management Studio. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-11-10 : 17:52:36
|
| Yes ,DDL TRIGGER |
 |
|
|
tc101
Starting Member
4 Posts |
Posted - 2008-11-10 : 18:00:27
|
| I meant some kind of management tool. Something like Visual Source Safe, that would work for SS 2005 on the internet. Maybe Visual Source Safe will do it. |
|
|
|
cvraghu
Posting Yak Master
187 Posts |
Posted - 2008-11-11 : 02:43:06
|
| Yes VSS/TFS would solve the purpose. But nothing prevents them from doing the changes directly in server. So it is better to bring a practice of checking out the code first and make the changes to file/server. Or restrict such things to very few people who will follow the process for sure. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-11-11 : 03:22:22
|
| the latter part can be ensured by implementing suitable policy. like only dbas wuld have access to run some sensitive code on production,... |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-11-11 : 05:17:41
|
| you could all also install this SSMS add-in and it would keep a local query execution history on disk and/or a central query execution history in one database. It saves every query that has been run.www.ssmstoolspack.com_______________________________________________Causing trouble since 1980Blog: http://weblogs.sqlteam.com/mladenpSpeed up SSMS development: www.ssmstoolspack.com <- version 1.1 out! |
|
|
|
uberman
Posting Yak Master
159 Posts |
|
|
shaunc
Starting Member
28 Posts |
Posted - 2008-11-11 : 16:37:06
|
| I use an application to export the DB schema out to scripts:http://www.codeplex.com/ScriptDBThen the script files live in a Subversion repository. When someone makes a change, they run the schema export utility and commit the changes to svn. Not only does this provide some accountability for who's doing what, it lets us grab a complete snapshot of the schema as it existed at any point in the past. |
|
|
|
|
|
|
Tool to keep track of changes made to code