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 |
|
cwalston
Starting Member
25 Posts |
 Posted - 2010-02-11 : 14:49:15
|
| Hi all, As our SQL Server environment has matured, we now have several DEV and QA groups building new things to get promoted into Prod. In the past, we've been able to handle the lessor amount of change, but the writing is on the wall that we need to manage it better. Things like version control, DEV/QA refreshes, and automatic deploys into QA and Prod are becoming critically needed. In preliminary discussions, my team has started going down the road of developing something that can do what we need. But before we do, I wanted to check to see if there is a tool out there that is widely used for such needs. I would greatly appreciate hearing what others are doing to manage their Production changes!Thanks so much! |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-02-11 : 15:02:11
|
| You can use a tool like RedGate DB Compare - to compare DEV with, say, QA and script the differences ...... but personally I think that scripting everything you do is the way forwards.We use Table Designer but ALWAYS use the Create Script button (rather than just pressing SAVE to make the changes). We save the script into a file with sequential increment ID in the filename. We can then run all such scripts, in order, on any server.Reason for suggesting this is that it is likely that you also have some "DML Data Adjustment Scripts" and no database comparison DDL tool can know about those.We store all Sprocs, Triggers, View etc. in separate files (rather than just Right-Click in Database Objects and press EDIT); they are part of revision control, plus we can make a list, in Modified Date Order, or which scripts have changed, and from that mke a deployment script (we have a batch file that concatenates a given list of files together) |
 |
|
|
|
|
|
|
|
Code Deploys into Production