Running Analyze from VSS 8 (VS2005 Beta 2) finds many many many errors in my VSS DB
Analyze from 6.0d in the verbose mode finds and fixes maybe two errors. The database is 3.7 GB, 83K+ files.
I copy the entire database to a new box with VS 2005 and run analyze using the same command line. The result is every conceivable error, hundreds of times, and each time I run it it writes out new copies of over 65000 files.
I have not gone into the client to see if this substantially mangles the database yet, as I'm on my third pass through the analyze process.
Has anyone else run analyze on their old db?
Dave in Colorado
Hi Dave,
Analyze v8 finds and fixes substantially more issues than analyze v6. However, once it fixes them (when "-f" flag is specified), next runs should not report the same errors.
What command line are you using when launching Analyze?
Is it possible you're specifying the "-c" flag? When you do, Analyze will rebuild every file in the database, creating backup copies. I wouldn't use that flag unless you really want to compact the files and save possible a couple kilobytes used by comments of deleted versions.
Alin
I was using the -c option. I've changed it so the parameters include:
-s -f -v4 and -b (and not -c anymore)
Now when I run it, the first time I get 8206 files and 213MB of files in the backup folder.
The second time I run it I get 5926 files and 74.5MB.
The third time I run it I get 37 files and 1.58 MB
The fourth time I run it I get exactly the same as the third, with the same messages and problems.
A cursory examination indicates that things are intact, but the third and fourth analyze did not fix the 16 or so lines containing the message: "The file (filename lists filname as a branch, but that file is missing or corrupted or doesn't have any parents or branches of its own."
Is there anything I can send anyone to aid in figuring this out?
Dave in Colorado
Hi, Dave.
with regards to your first question about files created in the backup directory, Alin is correct. -c or -s may force rebuilding of a lot of files. if you are seeing .backup files, that was a bug that will be fixed in the final release of SourceSafe 2005.
with regards to the second question about the error, analyze is apparently detecting that your files were branched, but the branched (2nd copy) does not exist. do you see analyze.bad in the backup directory? and if so, try running something like that analyze -f @backup\analyze.bad data and see whether it will address the issue.
let me know if this will work for you
thanks,
=Grigori
