Local Configuration Cache Overview

GENESIS can cache a local copy of a configuration database to reduce the number of times a SQL Server database needs to be accessed and protect against failure of the database or the network.

The configuration cache is very useful to redundant systems. The central configuration database for both redundant servers can be located on one of the servers, and the configuration cache will allow both servers to access the configuration even if the server hosting SQL Server has failed.

To enable or disable the configuration cache on individual components, open Configure Application(s) settings from the Home tab of the Workbench ribbon. In the Available Applications section, find the desired component and select the checkbox for Local Cache.

Before enabling the local cache for BACnet, set the GENESIS BACnet Query Interface service to Disabled in the Windows Services application. If the BACnet Query Interface is running when you turn on local cache for BACnet, GENESIS may create the BACnet cache file with no tables. (Stopping the service is not enough because applying the change starts it again.) After GENESIS builds the cache, you can set the service back to its desired startup type and start it.

The cached copy is stored in a SQLite database located at C:\ProgramData\ICONICS\11\Data\Cache. This database provides the caching by cloning all the configuration from SQL Server to this local SQLite database.

When a configuration is updated on the SQL Server, it triggers a sequence to automatically refresh the cache. This avoids synchronization issues and improves the chance of a cache hit (the chance of finding the data locally, which eliminates accessing the SQL Server instances). Also, there is no expiration time for the cached configurations; this implies that all data is always available.