Share via

Migrating from Another Version Control System to Team Foundation Server and Database Edition

  • Article

Before you put a database project under version control, you should decide which version control system best meets your business needs for managing database change. For example, Visual Studio Team System Team Foundation Server provides the most integration with Visual Studio Team System Database Edition. If you already have files in another version control system, you might be able to migrate those files and their version control history to Team Foundation Server.

For information about how to migrate from Visual SourceSafe to Team Foundation Server, see Migrating from Visual SourceSafe.

For information about how to migrate from ClearQuest to Team Foundation Server, see Migrating from ClearQuest.

If you are using some other version control system, you can still migrate your files to Team Foundation Server, even if you cannot migrate the version control history. You can create a database project, add any existing scripts, import your database schema from your production server, and then add the project to version control. This actually starts a new project. For more information, see How to: Create Database and Server Projects.

If you cannot migrate your file history to Team Foundation Server, you might be able to use your current version control system with Database Edition if it can connect through the SCCI providers in Visual Studio 2005.

See Also

Concepts

Terminology Overview of Database Edition

Other Resources

An Overview of Database Projects in a Team Environment

How to: Put Database Projects Under Version Control

An Overview of Database Creation and Deployment in a Team Environment