Strategy One
Improving Response Time: Caching
Strategy is retiring legacy administration tools in phases as capabilities move to Workstation, now available in the browser. December 2026 is last supported release for server legacy tools including, Developer, Command Manager, and Object Manager. For more information on legacy tool end of support, see Legacy Tools & Platform: End of Support Reference. For feature level details, see the Workstation vs Legacy Tools Feature Parity dashboard.
A cache is a result set that is stored on a system to improve response time in future requests. With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database.
Intelligence Server supports the following types of caches:
- Page caches: When a user views a published dashboard the Intelligence Server generates one cache per page, so that the cache can be hit when the user switches between pages.
- Result caches: Report and document results that have already been calculated and processed, that are stored on the Intelligence Server machine so they can be retrieved more quickly than re-executing the request against the data warehouse. For more information on these, see Result Caches.
Intelligent Cubes can function in a similar fashion to result caches: they allow you to store data from the data warehouse in Intelligence Server memory, rather than in the database. Intelligent Cubes are part of the OLAP Services add-on to Intelligence Server. For detailed information about Intelligent Cubes, see the In-memory Analytics Help.
- The History List is a way of saving report results on a per-user basis. For more information, see Saving Report Results: History List.
- Element caches: Most-recently used lookup table elements that are stored in memory on the Intelligence Server or Developer machines so they can be retrieved more quickly. For more information on these, see Element Caches.
- Object caches: Most-recently used metadata objects that are stored in memory on the Intelligence Server and Developer machines so they can be retrieved more quickly. For more information on these, see Object Caches.
You specify settings for all cache types except History List under Caching in the Project Configuration Editor. History List settings are specified in the Intelligence Server Configuration Editor.
Result, element, and object caches are created and stored for individual projects; they are not shared across projects. History Lists are created and stored for individual users.
To make changes to cache settings, you must have the Administer Caches privilege. In addition, changes to cache settings do not take effect until you stop and restart Intelligence Server.
For additional ways to improve your Strategy system's response time, see Tune Your System for the Best Performance.
