RE: [vault-list] Vault 2.0 Upgrade
Scott LaFave <[email protected]> Sun, 29 Feb 2004 09:11:40 -0500
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
Also much easier and more reliable on a move/copy to take the database offline or detach it. This removes the file locks on the mdf and ldf files. You can then copy/move the files to your new server and attach them using a sql command or enterprise manager. DTS does not work well at all for database copies. -----Original Message----- From: Lott, Douglas To: Chris Mullins; [email protected] Sent: 2/29/2004 7:06 AM Subject: RE: [vault-list] Vault 2.0 Upgrade it is much easier *and* reliable to move a database by using SQL Server's backup and restore functions. Doug Lott The Home Depot At-Home Services -----Original Message----- From: Chris Mullins [mailto:[email protected]] Sent: Sun 2/29/2004 12:53 AM To: [email protected] Cc: 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 Xf)+-XX(rX(rrj)fjb?X