|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
How to: Prepare your Visual SourceSafe Database for Running the Converter
Before you analyze or migrate your source-controlled files from Visual SourceSafe to Visual Studio 2005, you may want to prepare your Visual SourceSafe database.
To perform these procedures, you must have administrative permissions for the Visual SourceSafe database that you will migrate. For more information, see.
Preparing Your Visual SourceSafe Database for Running the Converter
To prepare your Visual SourceSafe database for migration, you should check in all files, fix any data integrity errors, back up the database, and decide which projects to migrate:
To prepare users for migration
Ask all Visual SourceSafe database users to check in their files.
To prepare projects for migration
Install Visual SourceSafe 2005 on the computer on which you are running converter. Visual SourceSafe 2005 is not installed by default when you install Visual Studio.
Copy your Visual SourceSafe database to a local folder on the computer on which you are running the converter. Although you can migrate a Visual SourceSafe database in a shared folder on a remote computer, the migration takes longer.
If your Visual SourceSafe database is a version earlier than Visual SourceSafe 6.0, upgrade it to 6.0 using the Visual SourceSafe DDUPD utility. For more information on the DDUPD utility, see the "DDUPD Utility" (http://go.microsoft.com/fwlink/?LinkId=59977) in the Visual SourceSafe Reference.
Fix data integrity errors. Use the Visual SourceSafe analyze utility to locate and if possible, fix any data integrity issues in your database. For more information on the analyze utility, see the "ANALYZE Utility" (http://go.microsoft.com/fwlink/?LinkId=59979) in the Visual SourceSafe Reference.