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 |
|
MattC
Starting Member
9 Posts |
 Posted - 2012-10-04 : 09:27:30
|
| I apologize if this is the wrong forum to post this question. If that is the case please point me in the right direction. :)The problem is simple, but the solution eludes me.I work in a shop with several other developers. We perform a release about every 2 months. During this time we resolve various maintenance and development related issues. When it comes time to do a release we typically have dozens of SQL scripts that must be run. In order to make the running of these scripts manageable for our customer we concatenate the various scripts together into one big file. When something goes wrong in the running of the scripts, or when the systems is restarted, it becomes extremely difficult to track down who made a particular change and why was it needed.This would seem to be a problem that a lot of other development/maintenance shops must be running into. The answer seems to be some sort of combination of source code control and documentation conventions. I'm interested in knowing how other organization have handled this. Is there some sort of lightweight documentation tool that can help? Can any of this be automated?Thanks in advance. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-10-04 : 10:30:03
|
| You should be using a source control tool for this. We make use of Microsoft Visual Sourcesafe for this. There are also tools from other vendors like SVN etc------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
|
|
|
Tracking Changes to SQL Files