I've moved your post to Server Administration , where I believe your questions will likely get more replies.
As for your questions,
1. Not really
Please refer to this onlinehelp Configure Data Connections
As for the extract location on server, please refer to this post Storage location of Extract in server?
Thank you, Lei! Some helpful articles and the right place for my question.
any other clarification needed?
I think I am understanding now...
-Live data connections, when published to Tableau Server, create a cache of data on Tableau Server.
-Connections to extracts, when published to Tableau Server, store the extract on Tableau Server.
If you have any additional information of note, or corrections to my understanding, let me know. Thank you!
Bravo, you got it!
Don't hesitate to reach out if you have further questions or concerns.
Does this create a security issue?
If the Live connection stores a cache and I don't have access to the database, am I able to see the cached view?
Likewise with extracts. If I don't have access to the published extract data source, can I see a view that is cached in a workbook that connects to the extract?
1 of 1 people found this helpful
Good questions Jennifer.
No, it does not constitute any security risks there. The same permissions would apply. Cached views are not independent of permissions.
As far as the extracts, those views are not cached. Even if they were, permissions would still apply and only able to see what you have permission to.
So I have another line of questions coming from the IT side of our institution, and I'm hoping you all can assist me in finding good answers. I have sent the documentation from https://onlinehelp.tableau.com/current/server/en-us/config_cache.htm in my initial email response to them. Here are their questions:
- As for the cached data, may we reach out to Tableau to determine if the cached data are used for performance improvement similar to most other AppServers where cached data has limited lifespan. Or is this a variation of cache where the data is stored permanently on the AppServer until it is manually refresh or remove by the operator?
- Depending on the finding from number 4, we may also entertain the option disabling the cache. Naturally, we do want to properly assess the performance impact of such option. We certainly would not want to introduce major impact to Tableau’s performance.
Based on the article I mentioned above, it looks to me like we can configure the Server to not keep data in the Cache for very long by using the "Balanced" setting. Hopefully that means we won't need to go down the road of disabling the cache. Is it even possible to disable the caching in Tableau Server?
Also, does anyone know if, with an enterprise license, we can run a separate development server without purchasing anything additional? I've also asked our Tableau representative - just wondering if you have any experience in this area.
1 of 1 people found this helpful
1. Cache server cannot be disables and it is indeed used for performance improvement as most webapps and has a limited lifespan by what you select under data connections.
As far as licensing, with your Tableau license, you are entitled to also have a DEV environment with the same key without any additional fees.
I have a requirement in which the data is changing real time based on the input from a web application.
If I connect to that table and create a live connection and develop a static view with few columns ,will it change the view exactly when new data is updated?.
We are planning to embed the visualization in same web application. Since I do not have any filters in my static view pivot visualization will it always show the data from cache? (as i am not changing any filter and query is not sent to database) Or will it have to wait till server refreshed the cache?.
To summarize my question will tableau can display live streaming data ie , will it display the data content as soon as there is a change in data or does it have to wait till the cache is refreshed?.
You can disable caching, either server wide or using a URL-parameter.
So you can have a live connection which can be refreshed to get the most recent data.