Starting Team Database Development
Before you can manage changes to database objects and settings or to server objects and settings, you must first create a database project or a server project. The project is the offline representation of the objects and settings for the database or server. For more information, see An Overview of Database and Server Projects.
You can import objects and settings from an existing database or server, or you can define objects and configure settings within the project that you just created. You then check in the project to version control, from which the team can build and deploy changes to isolated development environments. For an overview of how Visual Studio Team System Database Edition helps you manage changes to your database, see Managing Database Change.
The following table contains common scenarios that you might encounter when you start to develop databases in a team environment.
Your database does not refer to other databases, shared server objects, or SQLCLR objects.
Your database refers to at least one other database.
Your database refers to at least one SQL common language runtime (CLR) object.
Your database refers to shared server objects, such as logins or keys.
You want to manage changes to large databases.
Your database uses one or more XML Schema Collections.
The following table contains additional content that supports the previous scenarios.
Migrate existing database scripts: You can use your existing database scripts in another version control system to begin team development in Database Edition.