Second Level Cache

This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.

This topic provides overview of the Second Level Cache settings. Telerik Data Access has a caching mechanism, the 2nd Level Cache, which reduces the calls made to the relational server, by conserving data already loaded from the database. Database access is therefore, necessary only when the retrieving data is currently not available in the cache. This increases the efficiency and performance of your application. Caching for classes as well as for query results can be enabled using this section of the dialog, also the size of the cache can be set here.

• Enable the Second Level Cache - controls if the second level cache is enabled. Default value is False.
• Cache Query Results - controls if the second level cache should also cache query results. Default value is False.
• Maximum Number of Objects in Cache - controls the maximum number of objects which can be contained in the 2nd level cache. By default its value is set to 10000.
• Maximum Number of Query Results in Cache - controls the maximum number of queries that can be contained in the 2nd level cache. By default its value is set to 1000.

For more information about 2nd level cache, take a look at How to: Enable 2nd Level Cache (Visual Designer).