RE: Vault 2.0 Upgrade

After using Vault 2.0 for a day or so, I can happily reports that speed
is much better. 

VS.NET Integration (what I use for day-to-day operations) with 2.0 seems
to be 5x to 10x the speed of the older 1.2. 

It only takes 30 seconds to 60 seconds to load a big solution (20+
projects) which is a huge win. 

Someone there fixed some fairly serious integration bugs as well - the
whole "add existing item that is already source controlled" use case now
works, whereas before it was pretty ugly.

Congratulations on a great release and a very compelling upgrade. 

-- 
Chris

-----Original Message-----
From: Dan Schreiber [mailto:[email protected]] 
Sent: Sunday, February 29, 2004 2:50 PM
To: Chris Mullins; [email protected]
Subject: RE: [vault-list] Vault 2.0 Upgrade

Thanks for reporting back in Chris.  Sorry there were hiccups, but I'm
glad
all is well.

-Dan

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Chris
Mullins
> Sent: Saturday, February 28, 2004 11:53 PM
> To: [email protected]
> Subject: [vault-list] 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
> _______________________________________________
> vault-list mailing list
> [email protected]
> http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list