Video Screencast Help

How to configure EV to use the name of the new SQL Server

Created: 20 Feb 2013 • Updated: 20 Mar 2013 | 4 comments
This issue has been solved. See solution.
Hello People,
My SQL team has come up to me saying that existing SQL which host EV DB is having performance issue and have asked me to if we can migrate the SQL to a better H/W and x64 bit windows 2008 platform to overcome this issue
The config of the server is
Windows 2003 Std edition SP2
4 GB memory
SQL version 2005
Now my worries are that if we go ahead with SQL migration to new server how can i have my EV point to the new SQL server and have the same kind of information intact.
Though i found the article
HOWTO23565 Configuring Enterprise Vault to use the name of the new SQL Server that holds the Directory database
This does not make me comfortable,
Can you anyone please share their insight on how can i go ahead with this with minimal impact.
Discussion Filed Under:

Comments 4 CommentsJump to latest comment

GertjanA's picture

Hello Cdee

I have done several database moves from one SQL to another.

Main thing is COLLATION!!!!

Make sure your DBA team makes sure that the NEW SQL server has the same overall collation as the old one. If not, you're in for a not very user friendly excercise.

Check this document: It containes the required steps and necessary SQL scripts to change some databases. I have followed this several times, and this works without issues.

Verify collation:

Open SQL Management Studio, rightclick the Server Name, look at field Server Collation.

IT has to be the same on both. If not, and the 2nd does not have any databases, they way to change this is to re-install SQL, noiw use the correct collation.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS

Chris Warren's picture

On top of Rob's recommendations, I just wanted to let you know of a small caviate.  

If you are using a backup solution that utilizes a PSN (Partition Scan Notification) file (IE. Net Backup EV Agent), the EnterpriseVaultDirectory and EnterpriseVaultAudit DBs are expected to be in the same location.  Currently EV uses the location for the Directory to determine the location for the Audit DB for the backup location.

See the following:

I hope this helps.