My understanding is that the "Data cache refresh batch" batch job allows for caching of Workspace Tiles.
I have read Hatlevik's blog where he briefly describes this process as follows:
"The data cache framework is used to cache data sets and tiles. Enabling of the data cache framework will redirect certain queries against a cache table instead of executing them against the underlying source tables."
But I still have questions regarding this batch job :
1) What exactly does this process do?
2) What will happen if this job is not running. We had this issue, but there were no complaints regarding incorrect tile counts or workspace slowness.
3) Can this "Caching" cause an issue with Tile Counts (or anything else) where a tile count may not reflect a recent/current update?
You can see the cached entities here, under Data cache:
I haven't worked with instances where this has been an issue, as in your case, but from what I gather (and can read from the code), it will benefit workspaces that contain A LOT of transactions with complex queries. I can see the workspaces that it's used for are the bank management and general ledger workspaces.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.