Processing changes to the database schema

Question

I am in the rather early stages of creating an application that we hope will be sold in 1000 - it will probably be hundreds, but in any case more than enough to cause a good headache for changing the database schema.

I am rather limited to the Windows / .net / sql environment, as a number of our clients will host the application that I create on their web servers, and the extra bits installed on their servers never go well, and there is always a number of complaints / lost business as a result. So sqlalchemy is missing as it works in python.

What I need is a tool that will allow me to easily transfer between versions of the application. Ive found migrator.net, and Ive used it before, but never in production, as the development team seems to only work on it annually, and not a very active project.

What alternative approaches are available?

UPDATE I forgot to mention that I want to use this in a continuous integration environment, so when dude and sql data are compared with good gui tools, I really automate.

Answer 1

Visual Studio 2010 Ultimate/Premium Edition Visual Studio Team/Database Edition 2008, , Visual Studio.

(, dev prod) SQL Script . . script. , , . ( ). "" " " " ". http://msdn.microsoft.com/en-us/library/dd193250.aspx http://msdn.microsoft.com/en-us/library/dd193261.aspx , . , dev prod , prod dev.

Vinsual Studio Team Edition 2008 Visual Studio 2010 Ultimate. , . , 95% Visual Studio.

VS2010 Ultimate Premium, VS2008 Team Database Editions, http://www.red-gate.com/ (, http://www.red-gate.com/products/SQL_Compare/index.htm) .

Answer 2

Red_Gate SQl Compare .

, , , Source Control . SQL- , , . GUI. . , - 1, 2.3, , 2.3.

Answer 3

script. , , . :

CREATE TABLE SETTINGS(KEY VARCHAR(255), VALUE VARCHAR(255));
INSERT INTO SETTINGS VALUES('version', '1');

( , ) . 1 2; 2 - 3; 3 4 . script 1 3 , . ALTER TABLE CREATE TABLE, UPDATE.

Answer 4

SQL Compare , . : http://downloads.red-gate.com/HelpPDF/ContinuousIntegrationForDatabasesUsingRedGateSQLTools.pdf

Ideally, you would save your schema in the original control to get the most out of it, which you can do using SQL Source Control .

SQL Compare can migrate between two data, but source control provides a more mature development process .

If this does not reach what you are looking for, comment on this answer.