[In this post, I provide a previously undocumented method for dividing the contents of one database into two or more databases.]
Theoretically, the size of a SourceSafe database is limited only by the size of the partition on which it resides. If you're really inventive, you can probably even figure out how to make a VSS db span partitions... In practice though, Microsoft recommends that you keep your databases below 5 GB (and always on one partition).
If your database is larger than 5 gigabytes, you should run Analyze at least once a week and you should consider reducing its size. There are two ways to shrink a database. You can,
Methods for deleting data from a SourceSafe database are both manifest and well-documented but let's take a brief look at each. You can selectively delete SourceSafe projects and files using the Delete command (in combination with the 'Delete Permanently' option in the Delete file dialog box) in VSS Explorer or from the command line. From the command line, it is not possible to recursively Delete or Purge versions, files, or projects. A less obvious but arguably more effective way to delete data is the Rollback command, which destroys all versions of a file newer than the one selected. The Rollback command is available in the History window or from the command line. It makes sense to destroy data using the Rollback command if you store large binary files in your database (ie, .doc, .dwg, .xls, etc), if you're not too concerned about maintaining a cohesive history of your files and projects, and if you don't use the Share or Label features very often. If you do use Rollback to delete versions of a file from history, USE CAUTION, especially if you work for the government.
In most cases, it is safer and easier to move data rather than delete it. The documented method for moving projects from one database to another is as follows:
The Archive & Restore feature was designed to accomplish two tasks:
The Archive & Restore feature was not designed to make two databases from one. If you do need to split a database you need to know that Archive & Restore:
Unfortunately, there's no shipped workaround* for the first limitation. However, you can workaround the second limitation by splitting a database using the following method:
____________________________*Currently, it is not possible to migrate or copy a list of users and their concominant rights/assignments from an existing VSS database to another one, using either shipped VSS features or programmatically, using IVSS. However, our capable friends in Microsoft's Product Support Services (PSS) have developed a tool that can perform this task automatically. To download this tool, click here.
++++++++++++++++++++++++++This posting is provided "AS IS" with no warranties, and confers no rights. Microsoft kann für die Richtigkeit und Vollständigkeit der Inhalte in dieser Newsgroup keine Haftung übernehmen. Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ce message est fourni en l état, sans garantie d aucune sorte, et ne vous confère aucun droit. Vous assumez tous les risques liés à son utilisation. Il presente posting viene fornito così come é , senza garanzie, e non conferisce alcun diritto. ????? ?? ?????? "??? ????" ??? ?? ?????? ?? ??????, ????? ????? ?? ?????? ????.