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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-01-19 : 09:47:27
|
| Sergey writes "Hi All,Can you recommend a good version control tool or strategy for the following scenario?There is one development database and multiple test/customer databases. At some point all the schema and built-in data changes should be promoted for testing together with a build of the application (this is C# .NET application, but the specs of the app shouldn't matter for the DB versioning). After the changes are tested, they will be promoted to the corresponding customer databases.The problem: we need a tool to keep track of changes in DB, generate scripts, which will be used to apply this changes to customer test and production databases. Also the tool needs to promote new and changed rows in lookup tables, plus some build-in records in regular tables.There are several tools that solve the problem partially: Red Gate SQL Data Compare, SQL Source Control 2003, can anyone share the experience of using those?Thanks,Sergey" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-19 : 12:46:39
|
| I love Red Gate's tool. Their new version is much faster than their previous one. I use the Data Compare and SQL Compare tools to generate the code for me, but then I modify it. I do not use it for production though as it does things a little backwards sometimes. It gets the job done, but there is often a better way to make table changes. For example, to add one column to a table, you would use ALTER TABLE statement. The Red Gate tool will create a temp table with the new column, transfer the data to the temp table, drop the primary table, rename the temp table to the primary table name, etc... It just isn't needed to add a column to the bottom of a table. I use the tool often in development/test/non-prod environments to get those environments updated.Tara |
 |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2004-01-19 : 17:05:32
|
| The best way to track changes is to actually script them as they happen. It is quicker, more reliable and it gives you project history, and well, it's just better practice.Here is one such method (mine is fairly similar) http://www.nigelrivett.net/SQLServerReleaseControl.htmDamian |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-19 : 17:17:18
|
| I agree.I typically only use Red Gate's tools to prove that the environments are the same and also for those environments where the upgrade scripts aren't available (means that I wasn't the DBA on those). For all production work, I use my own scripts.Tara |
|
|
|
TimS
Posting Yak Master
198 Posts |
|
|
|
|
|
|
|
DB Version Control Tools