Visual SourceSafe Analyze - What happened?

Users were complaining of a couple minor erros in one of our Sourcesafe databases, so I ran the Analyze -c -f on the database.  I forgot to use the -v4 command to show what it found, so the only thing that it displayed when it was finished was:

Database analysis in progress @  5/04/09; 9:12p.
Analysis complete @  5/05/09; 2:43a
      Some errors or inconsistencies were found and fixed.

In the "backup" folder, it put almost 102,000 files!  They are mostly non-descriptive, small files.  Some are labled "A Files" some are labled "B Files" and some are just labelled "Files".  Are these 102,000 files "bad" or something?  How do I find out any additional information on what the analyze "fix" did?


By the way, our users are running Source Safe 6.0 and the Server is "hosting" with the 2005 version.
Who is Participating?
abelConnect With a Mentor Commented:
Don't worry about the version of SourceSafe, even the latest is still haveing the same codebase. The problems you'll encounter when using SourceSafe are numerous, and the necessary Analyze is only one of them.

As far as I know there is no way you can get more information about the fixes, unless you place back a backup of the whole database and run analyze again, but this time with a higher verbosity. But even then, I never found that I could do much with the information. Analyze is a strange thing and is basically a way for SourceSafe to correct its many errors that may arise.

My advice (maybe not what you're after, but I give it anyway): do what sourcesafe says: run analyze regularly, at least once per month. Make sure you have a very good full backup structure. Once things really go bad, you can't do much because sourcesafe uses a hard-to-read binary format, instead of the more common directory structure + files format that any other soruce control system uses.
jbobstAuthor Commented:
Thanks for the advice abel.  One other quick question, in the past, when I have ran the analyze tool, there were usually only a few files (maybe 3 or four?) that were put into the "backup" folder.  After the analyze last night, there are close to 200,000 files!  One difference is that I used the -c switch, when in the past, I only used the -f switch.  Could that be what caused all these files to appear in the backup folder?  And, are these files related to anything or are they just dead files?  What are they?
> One difference is that I used the -c switch


Cleans up and compresses unused space in the database. Compression removes blank space and does not compress the log files. Because compression generates a large number of files in the Backup directory, it should be used only when there is plenty of disk space available. Note that this option can be slow.
in other words, the amount of files is "expected". What they are? I'm not sure, I'll have to try it myself then, but my advice: just ignore them.

tx for the points :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.