Provides database versioning for SQL Server through vs 2010+SVN

For a software enterprise, the source code is the crystallization of all the wisdom of the company, must not have any mistakes. But how to manage the cornerstone database of the company's products? Typically, it is a way to back up a database file directly, or to generate a database deployment script to duplicate a backup. This method is feasible, but there are some areas worth improving. First of all, too cumbersome, wasteful spirit; second, inconvenient and other projects at the same time management. Here's a glimpse of the methods I stumbled across, and of course, a lot of people might have done it, but share it with people who don't know.

General ideas:

VS 2010 provides a project type that creates a new-> database->sql Server 2005 database object or SQL Server 2008 database object, providing the complete definition of SQL Server for creating and generating deployment scripts.

The Data-> architecture comparison (schema Compare) under VS 2010 Enables you to compare the differences between the SQL Server database and the server database project and provide bidirectional synchronization capabilities.

Subversion, which provides version-managed support for text-based SQL statements.

This example uses Visualsvn-server (Subversion server), ANKHSVN (the SVN plug-in vs 2010), SQL Server2005, vs 2010, and the sample database is AdventureWorks.

Because the installation is the English version of the VS2010, we correspond to the Chinese to see it.

First step: Create a database project through vs 2010. Open vs 2010,file->new->project, select Database->sql Server in recent templates, and select SQL Server Database in the project type to the right Project, enter the name of the item and click OK.

Step Two: Right-click on the new Examplesystemsql item, select the import Database Objects and Settings in the menu,