Vault 2.0 Upgrade

I took a bit longer than planned, but our Upgrade to Vault 2.0 went well
this evening. 

We had a few minor issues that other people may see, and SourceGear may
want to take a look at. 

During the upgrade process, we moved Vault to a new Machine. Following
advice gained here, we copied the SQL Database over to the new Vault
Server, and performed the upgrade. 

We tried to use the DTS to copy over the database from the original
machine, but kept getting failures. We were able to copy over the Tables
and the Data and all the SQL Objects (or so we though). 

The 2.0 installer got to the "upgrade database" phase, and errored out
with "sp_changepassword" not found. A quick checked in the DB, and sure
enough, the stored procedure is not there. DTS failed to copy the SP's
even though it said it had. 

Attempting to copy just the stored procedures using DTS resulted in
"success" being reported, but no stored procedures being created.
Possibly due to the encryption being used on them?

We then installed Version 1.2, launched the admin tool, and attempted to
restore the Vault Backup to the SQL Server. No dice, as the Vault Admin
tool didn't know anything about the backup and has no mechanism for
restoring from a file. This should be added...

We ended up using the SQL Enterprise Manager to restore the 1.2 backup
into SQL Server. This worked well. 

The Vault 2.0 install went smoothly from there. 


-- 
Chris Mullins