Upgrade Vaults To a Newer Database Engine
Occasionally, Accruent releases a newer generation of its database engines. Newer versions of Meridian might include small fixes to the database engines and upgrading is normally done as described in Upgrade Meridian Vaults. But large-scale optimizations take longer to develop and test and result in a new generation of engines. When this happens, you might want to upgrade a vault to take advantage of its new features and performance. Upgrading a vault to a new generation of database engine is typically not done during the normal vault upgrade process but must be performed manually.
An exception is when a vault that uses an older database engine (ObjectSet*.dll, ht3*.dll) is restored onto a 64-bit computer, the database engine is automatically upgraded to the latest database engine (ht5*.dll).
Manually upgrading a vault to a newer database engine can be done by either restoring the vault from a backup or by editing the Windows registry. In both cases, you specify a different database engine for the vault.
The filenames and descriptions of the different database engines are listed in the following table.
| Database Engine | Filename | Description |
|---|---|---|
|
First generation |
ObjectSet.dll |
Hypertrieve 32-bit |
|
First generation |
ObjectSQL.dll |
SQL Server 32-bit |
|
First generation |
ObjectORA.dll |
Oracle 32-bit |
|
Second generation |
ht3.dll |
Optimized Hypertrieve |
|
Second generation |
ht3sql.dll |
Optimized SQL Server |
|
Second generation |
ht3ora.dll |
Optimized Oracle |
|
Third generation (64-bit only) |
ht5.dll |
Multi-threaded Hypertrieve |
|
Third generation (64-bit only) |
ht5sql.dll |
Multi-threaded SQL Server |
|
Third generation (64-bit only) |
ht5ora.dll |
Multi-threaded Oracle |
This task should only be performed during non-production hours and after a verified backup of the existing vault is made.
Upgrade during Restore from Backup