SQL Server move and upgrade

[Aaron_Norton]

I am currently running Enterprise Vault version 10 on 2008 R2. I want to now move my SQL database information to 2008 R2 Windows and SQL. Is this possible to do or will the newer version of SQL break some items in the tables?

I have the article about moving databases was just curious if a newer version makes a difference. I am currently running it on 2003 R2 and SQL 2005.

Thanks for the info

[JesusWept3 · Accepted solution]

As always, first thing to check is the Compatibility Guides
http://www.symantec.com/business/support/index?page=content&id=TECH38537

On Page 14 it shows that Enterprise Vault 10 supports SQL Server 2008 R2, however R2 SP1 is currently Planned for support, doesn't mean that it won't work, or anything will break, but that it hasn't gone through QA and certified.

So if you have any issues and tried to call Symantec, they would simply tell you it's not supported, so cannot help until QA has completed the certification.

The being said, moving is pretty straight forward.
First and most importantly, make sure that the SQL Server you are moving to uses the same Collations as your current SQL Server, so check your current EnterpriseVaultDirectory databases collation, and when installing the new server, change the collation to use whatever EnterpriseVaultDirectory uses.

If you don't then you may have a collation mismatch, it will show a warning in the Deployment Scanner, but more importantly, it may actually cause a lot of errors and other issues, especially if you end up using a Case Sensitive Collation that will break a lot of things.

The procedure for moving is pretty straight forward.
1. Run Deployment Scanner to check for correct permissions and connectivity
2. Stop all EV Services on all EV Servers
3. Go to  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Enterprise Vault\Directory\Directory Service
4. Edit the "SQL Server" registry key to reflect the new SQL Server (Do this on all EV Servers)
5. Open a SQL Management Studio and then do the following
6. Edit the "SQLServer" column in the FingerPrintDatabase table
7. Edit the "SQLServer" column in the MonitoringSettings table
8. Edit the "SQLServer" column in the VaultStoreEntry table
 

Regarding steps 3 and 4, edit the registry and NOT the ODBC DSN connections as EV Will recreate them based off whats in the registry, so if you just edit the DSN's, then EV Will reset them back and the connection will fail

[JesusWept3]

And some further reading for you:

How to move Enterprise Vault databases from one SQL Server to Another
http://www.symantec.com/business/support/index?page=content&id=TECH35744

How to move a Fingerprint Database for Enterprise Vault
http://www.symantec.com/business/support/index?page=content&id=TECH64655
 

[LCT]

Here's what you need: http://www.symantec.com/business/support/index?page=content&id=TECH35744 Just a few notes: When you install the new SQL server, ensure that the SQL Collations matches the current EV databases, you can check going into the properties of a current EV database. Of course make the usual VSA being member of the local admin group and have dbcreator rights on the new SQL server. Moving SQL 2005 database to a SQL 2008 server is not a problem either, ensure that compatibility level is set correct (100 for SQL 2008). Hope that helps.