How do you manage your sqlserver database projects for new builds and migrations?

Posted by Rory on Stack Overflow See other posts from Stack Overflow or by Rory
Published on 2010-04-20T13:50:59Z Indexed on 2010/04/20 13:53 UTC
Read the original article Hit count: 232

How do you manage your sql server database build/deploy/migrate for visual studio projects?

We have a product that includes a reasonable database part (~100 tables, ~500 procs/functions/views), so we need to be able to deploy new databases of the current version as well as upgrade older databases up to the current version. Currently we maintain separate scripts for creation of new databases and migration between versions. Clearly not ideal, but how is anyone else dealing with this?

This is complicated for us by having many customers who each have their own db instance, rather than say just having dev/test/live instances on our own web servers, but the processes around managing dev/test/live for others must be similar.

© Stack Overflow or respective owner

Related posts about sql-server

Related posts about sql-server-2005