Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VSS Maintenance Analyze

Status
Not open for further replies.

Shell02

Technical User
Nov 6, 2002
53
US
I found an article on MSDN that suggests running analyze switches in the following order provides good coverage:

analyze -v4 <database path>
analyze -f -v4 <database path>
analyze -f -c -v4 <database path>

If I know that there are errors that need to be corrected, is there any reason why I shouldn't run the analyze -f -v4 <database path> right away? And if I know I have &quot;found a diff&quot; and &quot;found a comment&quot; errors, is there any reason why I shouldn't run the analyze -f -c -v4 without running the previous two?
 
Probably not but, since this is your code, caution is in order. In general, I'd suggest the following:
1. Make a full backup of the VSS db.
2. Restore this backup to another location.
3. Run Analyze against this duplicate. If your db is large, Analyze may take a long time when run with the -f
switch. You can minimize the time by running it without the -f switch. After it completes, there will
be a file named analyze.bad in the data\backup directory. Copy this file to the folder containing analyze.exe. Delete
analyze.bad from data\backup and then run
analyze -f@analyze.bad <path to your data directory>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top