DB Source Control? 1

[adamroof]

Hi everyone,

What tools do the MSSQL pros use for working on a database in a development environment? Whats the best way to know whats been updated so you can apply to a production db?

Right now i am just generating alter statements from notes i've written down.

 

[markros]

Check

http://forum.lessthandot.com/viewtopic.php?f=17&t=4618

for some ideas.

 

[markros]

Recommendation from another forum for a free tool

http://www.yessoft.com/software/sqlservercompare/sqlservercompare.htm

 

[adamroof]

Perfect, thanks! I knew i couldnt be the only one with the same question, but my intergoogle skills failed me on the search.

Ideally, the changes to the Test database would be applied through a tool that automatically saves the script, so you're not relying on developers to remember to log their script in your script-collecting tool.

This is so true even for the single developer environments!

I have all the code (DDL and procs) in SVN and then go from there, scripting the changes out and running that on prod when we are ready to deploy

SVN along with the SQL compare seems to be a magical solution, at least then i can diff the scripts!

I already use the DBComparer.

 

[SQLSister]

We make all our databases changes through scripts that are put into Subversion for source control. When we deploy a change, all our database changes are grouped with all the other code changes in the deployment folder and deployed. Developers don't have rights to prod, so no changes are ever made except through scripts.

"NOTHING is more important in a database than integrity." ESquared