Currently we have our Vault database installed on a Windows Server 2003 SP2 OS with SQL 2005 server SP2 on it. We want to "move" our database to a NEW server (Windows Server 2008) that has SQL 2008 SP1 on it. While I am familiar with SQL backups and restore, I am concerned and not sure how to change the "bindings" for Vault Admin and Vault client.
Do I simply uninstall the Vault Admin tool (leaving the DB in tack) and reinstall pointing to the new database on a different machine? And will this change the bindings? Or is there an easier way?
Current Setup
Vault ADMIN is on BOX B Windows Server 2003 Enterprise SP2
Vault DB is on BOX B Windows Server 2003 Enterprise SP2
Vault clients are developers on a host of PCs
New Setup
Vault ADMIN is UNCHANGED
Vault DB is on BOX NEW Windows Server 2008 wit SQL server 2008 STD Edition SP1
Vault clients are UNCHANGED
Thanks, you guys are the best!
Steps involved in Moving Vault Database 5.1.1
Moderator: SourceGear
Re: Steps involved in Moving Vault Database 5.1.1
I think by Vault Admin, you probably mean the Vault Server. The Vault Admin Client is a web client and connects to the Vault Server from anywhere.
To move the Vault databases (sgvault and sgmaster) to a new SQL Server machine, we'd recommend uninstalling Vault, leaving the databases, then moving the databases to the new SQL Server. Next, reinstall Vault, pointing it to the new database location. Details here:
http://support.sourcegear.com/viewtopic.php?t=924
If SQL Server is on a different machine than the Vault Server, your options depend on what you want to use for your SQL authentication:
--Windows authentication -- use a custom (domain) account for the IIS process model user, then choose Windows authentication in the SQL Server setup portion of the installation.
--SQL Server authentication -- choose SQL Server authentication in the SQL Server setup portion of the installation. The installer will ask for your SQL Server SA credentials so that it can create an sgvaultuser account for Vault to use to communicate with the database.
Since Vault Clients and the Vault Admin Web Client will be connecting to the same Vault Server, you should have to change any bindings or Vault server urls that you use for connecting.
Let me know if you have additional questions.
To move the Vault databases (sgvault and sgmaster) to a new SQL Server machine, we'd recommend uninstalling Vault, leaving the databases, then moving the databases to the new SQL Server. Next, reinstall Vault, pointing it to the new database location. Details here:
http://support.sourcegear.com/viewtopic.php?t=924
If SQL Server is on a different machine than the Vault Server, your options depend on what you want to use for your SQL authentication:
--Windows authentication -- use a custom (domain) account for the IIS process model user, then choose Windows authentication in the SQL Server setup portion of the installation.
--SQL Server authentication -- choose SQL Server authentication in the SQL Server setup portion of the installation. The installer will ask for your SQL Server SA credentials so that it can create an sgvaultuser account for Vault to use to communicate with the database.
Since Vault Clients and the Vault Admin Web Client will be connecting to the same Vault Server, you should have to change any bindings or Vault server urls that you use for connecting.
Let me know if you have additional questions.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Steps involved in Moving Vault Database 5.1.1
Linda:
In your last statement....
Since Vault Clients and the Vault Admin Web Client will be connecting to the same Vault Server, you should have to change any bindings or Vault server urls that you use for connecting.
Did you mean you "SHOULD NOT HAVE TO"....?
Meaning, no change is required on the Vault Clients, right
In your last statement....
Since Vault Clients and the Vault Admin Web Client will be connecting to the same Vault Server, you should have to change any bindings or Vault server urls that you use for connecting.
Did you mean you "SHOULD NOT HAVE TO"....?
Meaning, no change is required on the Vault Clients, right
Re: Steps involved in Moving Vault Database 5.1.1
Sorry, you're right. I meant "you should not have to . . ."
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Steps involved in Moving Vault Database 5.1.1
OK Thanks for your help. Have a nice day.
Re: Steps involved in Moving Vault Database 5.1.1
You're welcome. Let me know if you need anything else.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager