What are the steps involved in upgrading a VSS database from 6.0d to 8.0?
I have a number of VSS6.0d databases (the code goes back around 6 years or
so), and while the latest version of all the files is what I want, it would
be nice not to lose the history of changes.
I have made backups (of course), but I don't think that just pointing to the
old database is right, because my scheduled analyze runs give me the same
error someone else (Bryan Donaldson) has previously (9-May) reported:
Running advanced reference verification.
The file S\DATA\\ is not a valid SourceSafe physical database file. It must
be renamed to a file with an extension or moved to another directory outside
the database.
The file S\DATA\\ is not a valid SourceSafe physical database file. It must
be renamed to a file with an extension or moved to another directory outside
the database.
Validating references.
Analysis complete @ 5/09/07; 7:02a
Some errors were found: run ANALYZE -F to fix these problems.
I'm guessing that there's something like DDUPD that I need to run to upgrade
it, but I'd appreciate any pointers before I go and trample all over it.
Thanks in advance

Signature
Steve S
Mark T - 05 Jun 2007 15:43 GMT
> What are the steps involved in upgrading a VSS database from 6.0d to 8.0?
> I have a number of VSS6.0d databases (the code goes back around 6 years or
[quoted text clipped - 27 lines]
>
> Thanks in advance
The database is the same format between 6.0d and VSS 2005. The error you
are seeing is a known bug and can be ignored, but to get rid of it, rename
the aaaaaaaa file in the <database>\data\a directory to all upper-case. You
will have to do this each time you run the analyze utility with the -c
option.
--Mark
SteveS - 06 Jun 2007 11:31 GMT
> The database is the same format between 6.0d and VSS 2005. The error you
> are seeing is a known bug and can be ignored, but to get rid of it, rename
[quoted text clipped - 3 lines]
>
> --Mark
[fx: checks to see if it's 1st April]
I'd hate to see the code responsible for that. Presumably someone's doing a
case-sensitive comparison on a filename returned by a file enumeration
operation....
Thanks
Steve S
WenYuan Wang [MSFT] - 06 Jun 2007 09:04 GMT
Hello Steve,
Thanks for Mark's quickly reply.
Actually, as Mark said, the error you meet when using Analyze.exe utility
is a known issue. Below is the document about this product issue.
http://support.microsoft.com/kb/923842/en-us
[FIX: Error message in the Analyze.log file when you run the Analyze.exe
utility in Visual SourceSafe 2005: "The file 0\DATA\\ is not a valid
SourceSafe physical database file"]
Supported hotfix is now available from Microsoft. To resolve it, you may
contact CSS directly to obtain the hotfix.
By the way, for upgrade issue, you may also check the following article
about DDUPD.
http://msdn2.microsoft.com/en-us/library/x8d2h3te(VS.80).aspx
[How to: Upgrade a Database]
Hope this helps, please let me know if you still have anything unclear. We
are glad to assist you.
Have a nice day,
Sincerely,
Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.