How to move Discovery Accelerator and Analytics databases to a new logical drive on the same SQL server.

Problem

How to move Discovery Accelerator (DA) and Analytics databases to a new logical drive on the same SQL server.

Cause

The Analytics feature of Enterprise Vault's Discovery Accelerator uses the SQL full-text index catalog feature to index the data captured within the Case or Research Folder for which Analytics was enabled.  One of the files used by the SQL full-text index catalog has the NDF file extension.  Each Analytics enabled Case or Research Folder has its own set of full-text index catalog folders and files that can grow to be very large when several thousand or million items that have been captured within the Case or Research Folder.

Various issues can arise that necessitate the need to move a Discovery Accelerator (DA) customer database from one SQL Server machine or instance to another SQL Server machine or instance with a SQL Server instance move being on the same SQL Server machine or a different SQL Server machine.  For example, the drive containing the customer database and its full-text index catalog files and folders may be running out of space and company policy would be to move the associated files and folders to a new SQL instance with its files and folders on a different, larger drive.

The preferred process to move a DA customer database includes the step to disable Analytics on all Analytics enabled Cases and Research Folders, but completing that step is optional and sometimes impractical.  When Analytics must remain enabled, the database move process must include the associated full-text index catalog folders and files that include the applicable NDF file.

The following information provides a guideline of the recommended actions needed to move a DA customer database with full-text index catalog files and folders present from one SQL instance to another SQL instance on the same SQL Server machine.
 

Solution

It is recommended to remove Analytics from all research folders and cases prior to moving DA databases.  
When the removal of the Analytics database on a Case or Research Folder is time prohibited, then moving the Analytics database may be preferred.

There are certain restrictions to moving the Analytics database:
  • Analytics folders and files must be on a local drive (for example, a physically attached drive or SAN attached drive referenced through a local drive letter)
  • Analytics folders and files must not be located at the root level of the local drive
  • Analytics folders and files must be located on the same SQL server as the DA customer database but can reside on a different drive or drives than the DA customer database
  • The requirements and steps must be followed according to Microsoft's recommendations.  For SQL Server 2005 and greater, refer to Microsoft's MSDN article on 'Manage Metadata When Making a Database Available on Another Server Instance (SQL Sever)' https://msdn.microsoft.com/en-us/library/ms187580.aspx

Moving the DA customer and Analytics database(s) to a new logical drive on the same SQL server

1. Ensure that full-text indexing is not currently in the process of enabling/disabling any Case or Research Folder.  The following query, run against the DA customer database, should return no results before continuing with the move of databases.
SELECT CaseID, [Name], AnalyticsStatusID FROM tblCase WHERE AnalyticsStatusID NOT IN (851, 856)

2. Create a folder location on the new local drive for Analytics.  The DA database can reside here as well.

3. Stop the Enterprise Vault Accelerator Service (EVAMS)

4. Detach the DA customer database

5. Move the Analytics database(s) and folders to the new folder location on the new local drive

6. Move the DA customer database and transaction log(s) to the new drive location

7. Attach the DA customer database, log files and Analytics databases to SQL
- each Analytics database (ndf) will need to be pointed to its new folder location
When SQL popup window asks if you want to locate the full-text catalogs, select YES
- point each of the full text catalogs to their new location.

8. Start the EVAMS

9. Open the EVBAAdmin webpage

10. Open the properties page of the DA customer and edit the SQL Server and the Database Locations For Analytics  

11. Restart the EVAMS
 
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)