Need to relocate Directory Database to other SQL-server - possible?

[GertjanA]

Hello all,

In our environment there seems te be an issue with the sql-server being busy. DBA's would like to move only the directory database to another (less busy) sql server.
Is that possible? The other db's would remain on the original server.

I assume that the steps to be taken are to update EV to point to the directory server (also in registry), but how about the stores? Do they need updating too?

Does anyone know of an kb-doc available on this?

Thanks.

[JesusWept3 · Accepted solution]

for the directory, just move the database and then update the registry to in \Directory\Directory Service\SQL Server and change the name make sure that the EVAdmin has the rights to db, is a db_creator etc if you move the vault store databases, you just have to update the VaultStoreEntry table don't bother changing the DSN's, the admin service will do that itself based on whats in the registry and the enterprisevault directory database the fingerprint database is the trickier one to move

[JesusWept3]

oh and the kb is here
http://seer.entsupport.symantec.com/docs/273272.htm

[RahulG]

http://support.veritas.com/docs/340611

[GertjanA]

Found those docs also. I was curious to see of anyone had a setup with databases split between several sql-servers.

Thanks again.

[JesusWept3]

yeah you'll be fine, the only thing i would watch out for is if you run a cross SQL Server / Cross Database query such as  the following that would give you a mailbox name based on a transactionID


SELECT EME.MbxDisplayName
FROM SQLServer1.EnterpriseVaultDirectory.dbo.ExchangeMailboxEntry EME,
            SQLServer2.EVVaultStore.dbo.Saveset S,
            SQLServer2.EVVaultStore.dbo.ArchivePoint AP
WHERE S.ArchivePointIdentity = AP.ArchivePointIdentiity
       AND AP.ArchivePointId = EME.DefaultVaultId
       AND S.IdTransaction = '12345678-1234-1234-1234-123456789012'


If you perform the above query it may fail because you need to use sp_addlinkedserver so that they "trust" each other
http://msdn.microsoft.com/en-us/library/aa259589(SQL.80).aspx

That really is the only downside that i can see

[GertjanA]

Thanks JW for the heads up.