EV 2007 - SQL database setup

[eama]

EV 2007 single site across geographic locations.  What are the issues involved in standing up a second SQL server to house just the local vault store database(s) so we don't have to traverse the wan.  Will this work as expected, journaling traffic will write locally to the database.  Only site config changes will go across the wire to the dir database.   DA will just see a new vault store although the db is on a different SQL server.  IS there any ongoing chatter between the 2 SQL servers.   Thanks.

[MichelZ]

Yes, I think this will work, and is even recommended. No chatter between SQL Servers.

[Nick_White]

There will still be calls to the Directory database from the remote server, so no calls is not strictly correct, but it will definitely minimise the amount of traffic and will work just fine

[eama]

Do you know how frequent these calls are made and for what purpose?  Thanks for the response.

[JesusWept3]

calls between the vault store databases and the directory database are going to happen constantly.

So for instance lets say you have the following

SQLServer.siteA.com <--- Directory database
SQLServer.siteB.com <--- Vault Store database
EVServer.siteB.com <--- EV Server

If you go to

http://evserver.siteb.com/EnterpriseVault/ArchiveExplorerUI.asp

The very first thing its going to do is its going to do is start enumerating between the Vault Store database and the directory database to find which archives you have access to, then to build the TreeView it will go to the EnterpriseVaultDirectory database and go through the archive folder table.

After that when you click an a folder, it will then pull settings from the IndexVolume table to determine the index locations and what not, then query the index to give you a list of items in your archive.

Once you click an item, say you have preview pane on or you open an item, its then going to call the item from the vaultstore database, but part of that check will be to check permissions anyway, so it will link from vault store to enterprise vault directory.

Also any time you sync a user it will update both EVD and Vault store
Any time delete an item, delete a user, sync a user, run vault cache, run storage expiry, manually archive an item, restore an item, open outlook, etc etc, it will link the VSDB to the EVD

It's unfortunately unavoidable, if the link is really really really that slow though, you may be best off with an entirely different site, however that may be premature, cos it would be all based on the link speed between both sides, utilization, how many users in both sites etc

[eama]

Thanks for the info!  The link is fast but a half utilized already.  But this new location and vault store is only going to be used to migrate data from another archiving system through a journal mailbox, then just be a repository for DA from there on out.  So I don't see much traffic between EVD and VSDB, do you?

[JesusWept3 · Accepted solution]

yeah you won't see that much, but you can guarantee that almost every call made to the VSDB or the DA database will interact with the EnterpriseVaultDirectory, its unavoidable, but i doubt you'll notice it