![]() Our Database: Analyze hasn’t been run on our database since 2004 (if ever).ĭuring the VSS to Subversion conversion Analyze was run on a copy of the VSS database and it showed many files had corruption in their history. You should run it as frequently as is practical-once a week is recommended, or at a minimum, once a month. Best Practice: Use the Analyze tool shipped with Visual SourceSafe to detect and repair problems in the database structure… you can discover small problems and fix them before they become worse. Our Database: The VSS database that our source code is in is currently 25 GB.Ģ. Best Practice: Visual SourceSafe database should not exceed 3 to 5 GB Visual Source Safe Best Practices and Our Database:ġ. Many factors can cause a SourceSafe database to become corrupted. On Microsoft’s site they have the following warnings: In general Visual Source Safe is known to have problems when the database gets large, if there are a lot of users, or if it is used over a network. Our experience with the Visual Source Safe to Subversion conversion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |