HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Hypertrieve

If 0 (default), property count is limited to 32,768 entries. If property count exceeds this value, the engine will be stopped. To repair the situation, it is possible to increase the limit by setting this registry entry to a non-zero value.

The absolute maximum is 65,535 properties. Beyond that the vault cannot be opened anymore.

Having so many properties in a vault is not normal. Usually this is caused by many different sequence names being generated in script. If this situation occurs, the use of sequences in script should be changed. If that many different sequences are needed, an alternative method should be considered, such as generating sequence numbers using a SQL database.

If old sequences are not needed anymore, they can be removed from the vault using the ImportFilterFile registry setting.

Number of database calls beyond which a transaction is deemed to be a batch transaction. Default = 500, 0 = no load balancing. See Optimize the Meridian Server Software and Configure the BatchCallThreshold Setting.

If this value is 1, enables extra runtime low-level data consistency checks to be performed and reported to event log. Significantly decreases database engine performance. If this value is 0 (default), disables extra consistency checks at runtime.

If this value is 1, a memory dump file is generated that can be sent to Accruent Technical Support for troubleshooting. If this value is 0 (default), no file is generated.

If this value is 1, allocates extra memory to debug memory overwrite problems. If this value is 0, disables extra consistency checks at runtime.

Not used.

If this value is 1, duplicate records are checked during VCW repair but not reported. If this value is 0 (default), duplicate records are reported. For internal use only.

If this value is 1, forces engine to dump compartment allocation information when database is closed. If this value is 0 (default), disables dump.

If this value is 0, skips restore when opening a database containing inconsistencies. If this value is 1, restores the database by executing the log file with the most recent snapshot.

If this value is 1, uses old, slower repair algorithm during VCW repair. If 0 (default), uses new algorithm.

If this value is 1, enables page allocation tracing. If this value is 0 (default), disables tracing.

If this value is >0, enables call logging using special SetVariant. Calls can be logged at runtime by setting any string property to TRACE:+ or TRACE:- to turn it on and off. If this value is 0 (default), disables logging.

If this value is 1, indexes strings using datagrams, which speeds up pattern matching. If this value is 0, does not use datagrams.

Controls generation of extended event log messages.

The following values are supported:

0 – no extended messages are logged (default)
1 – log extended messages when cache loader threads fail
2 – log extended messages when DLLs are loaded and unloaded
3 – log both types of extended messages

When a transaction exceeds the BatchCallThreshold number of database calls, it will be made to wait after each call for as much time as it has spent. The total wait is partitioned in individual waits of WaitInterval milliseconds. Default = 3.