Microsoft KB Archive/221118

= How To Upgrade a VSS5 Database to VSS6 Using Archive Utility =

Article ID: 221118

Article Last Modified on 7/13/2004

-

APPLIES TO


 * Microsoft Visual SourceSafe 6.0 Standard Edition

-



This article was previously published under Q221118



SUMMARY
This article describes an alternative to using DDUPD.exe when updating a database from Microsoft Visual SourceSafe (VSS) 5.0 to VSS 6.0 format. The process involves archiving a VSS 5.0 formatted database and restoring it to a new VSS 6.0 formatted database.



MORE INFORMATION
A new database can be created either using the VSS 6.0 CD and performing a server install or from the Visual SourceSafe 6.0 Administrator by selecting from the Tools menu Create Database. The second method creates a basic install including only the Users.txt and Srcsafe.ini files along with the data, temp, and users directories.

In the VSS6 Administrator tool you can select a database from the Users menu and then select Open SourceSafe Database. You should start by opening the VSS 5.0 database that you intend to upgrade. (VSS6 Explorer and VSS6 Administrator tools can read VSS5 formatted databases.) You should then select the menu item from the Archive menu and then select Archive Projects. This takes you through a three-step process.




 * 1) The root project should be selected. Click OK and then Next.
 * 2) The Save data to a file option should be selected by default. Type a name for the archive file *.ssa in the space provided and click Next.
 * 3) The Archive all data option should be selected by default, click Finish.

You should then select the new VSS6 database and select the menu item from the Archive and then select Restore Projects. Again, this starts a three-step process.

 Select the name of the archive file - *.ssa. You may get the following message:

"Destination database is not the same as the original. Some links may not be restored."

Click OK and then click Next. Select Display subprojects checkbox and unselect $/. Click Next. Click Finish.

This type of conversion process requires you to re-add all user and users rights since the new database will only have the admin and guest accounts setup.

NOTE: Sometimes it is necessary to archive the database in parts. If you decide archive in parts you will lose any shares and branches between files that are in projects archived separately.

