SSAnalyzer is a unique management and analysis tool for Microsoft's Visual SourceSafe.

SSAnalyzer provides a number of tools to identify and correct common (and numerous) user-caused problems within Visual SourceSafe. These include:

Identification, recommendation and correction of inappropriately branched files caused by file version rollbacks (implicit branching).

Identification, recommendation and correction of inappropriately branched files caused by file version branching (explicit branching).

Identification, recommendation and correction of duplicate or near duplicate files caused by get/add vs. share resulting in unnecessary code duplication and maintenance.

Global presentation and purging of deleted files and projects, thereby reducing the possibility of these files being erroneously recovered.

SSAnalyzer is a software tool specifically designed to help software development managers at all levels to identify and easily correct common, yet costly, conditions within Visual SourceSafe. These conditions are typically, yet unintentionally, caused by users through the normal use of SourceSafe. A couple of poor user procedures can lead to costly debugging and recovery efforts.

SSAnalyzer Main Features:

---

Within minutes, import your SourceSafe repository transactions into an MS-SQL database

Provide global view of projects and files from several key aspects

Provide GUI to assist user in quickly identifying and correcting several potential and costly problems:

• Different files with same file name.
• Files inappropriately branched due to a rollback of a shared file
• Deleted but unpurged projects
• Deleted but unpurged files

Provide valuable and quick clean up options on SourceSafe in order to obtain:

• Reduced maintenance costs by eliminating unintended code/file duplication
• More accurate reporting by various third party packages (CodeReports, SourceVizor) by eliminating unintended code/file duplication
• Faster SourceSafe response time due to reduced number of projects and files in the repository
• Identify undesireable coding habits (copy and modify vs. refactoring vs. use of #define) that individual developers may be employing. (Need some training)