Cache: Repository object properties

Repository objects that process data from DBMS, use various caching types to speed up the work. If an object is parametric, the instances for each parameter set are saved. When opening the object the required data instance will be taken from cache. If some data was changed, it will be updated in cache and DBMS. When object structure is changed, the use of saved cache instances is unavailable.

NOTE. It is recommended to delete saved instances using the Clear Cache button each time the structure changes. The instances will be saved for a new object structure in this case.

Select the Properties item in the object's context menu.

To cache an object:

Select the Cacheable Object checkbox.
Select a database that will store cache. If the database is not selected, the cache is saved to the current repository database.

NOTE. The Database parameter is displayed if the user works with global cache. If in the InMem section of the settings.xml file or in system registry settings the CacheType parameter is set to file, the Database parameter is not displayed.

As a result, object caching is set up.

NOTE. Cube caching is executed based on a display version selected by default. If you have changed a default display version, execute cube caching again. Various dictionary types and MDM dictionaries use their own caching mechanism by default.

To update cache, click the Update Cache button.

TIP. To update cache by schedule, use task scheduler.

To clear cache, click the Clear Cache button.

NOTE. The database to store cached objects must be based on one of the following DBMS: Microsoft SQL Server, Oracle, PostgreSQL/Postgre Pro. DBMS version must correspond to one of the supported versions.