Migrate a Hypertrieve Vault To SQL Server

To migrate an existing Hypertrieve vault to SQL Server:

1. Create a new vault as described in Create a New Vault using the options described in the following table.

2. Confirm the migration was successful by checking the new vault for:

   • Total number of documents equal to the source vault

   • Existence of prior revisions

   • Correct status of work in progress documents

   • Documents are visible in the Meridian viewer

   • Custom configuration items

3. To prevent users from accessing the old Hypertrieve vault instead of the new SQL Server vault, delete the Hypertrieve vault in the Meridian Enterprise Administrator.

Vault migration options

Option	Value
Database engine	Microsoft-SQL
Import contents from another vault	Enable
Source Vault	Select the Hypertrieve vault
Copy stream files	Enable
SQL Server computer	Type a SQL Server computer name

After the migration is done, the new vault is ready for use.

The migration can take a significant amount of time, depending on the size of the Hypertrieve database and the number and size of the stream files. The size of the resulting SQL Server database will be about 2.5 times the size of the source Hypertrieve database and can be seen in Windows Explorer in the location specified for the Path for database files property of the vault.