Hi Sunil Tikar,
As we discussed this exact question earlier with a customer, i'll share the details with you:
Is there a way I can keep my live connection without much caching, while caching the views using extracts for as long as the extracts do not change? Does it even make sense to talk about caching when using extracts? If so, is the caching 'automatic' (cached until the extracts is refreshed), or also controlled by the 'Data Connections' configuration tab?
No. You can't tell one data source (SQL Server, Oracle, whatever) to cache one way, and a different data source (extracts) to cache another.
You can read more here as well
Lénaïc RIÉDINGER, Global Community Engineer Tableau
If you see a Helpful or Correct response, please mark it thanks to the buttons below the targeted post!
Thanks for sharing this. Does it means Cache does play role when view renders based on TDE ?? I am asking this again because I am unable to find anything about "extract caching" on tableau documents which states explicitly that " Cache option we applied at server level (refresh more often,less often or balanced) applies to both TDE based report as well as Live connection dashboards" .
Yes it does
Also for example, "Refresh less often" means Cached data sticks around for up to 12 hours. There are a fair number of situations where the cache is expired and/or lost.
- The data source is modified
- A viz with an embedded data source is re-published
- Tableau Server is restarted
- An extract is refreshed (this counts as a modified data source as far as we're concerned)
Some more details here: Data in a Tableau Server View is Out of Date | Tableau Software