This could very well be expected behavior based on how Tableau Server's cache settings have been configured. An "out of the box" installation of Tableau Server will have Caching set to "Refresh Less Often" (as seen in the "Data Connections" tab of the Tableau Server Configuration tool.
"Refresh less often" essentially means "Keep the data you have indefinitely unless someone manually refreshes" - which you've been doing with the Refresh button.
If you don't want Tableau Server to do any caching (always query Aster Data, no matter what), you can choose "Refresh More Often" in the Data Connectiosn tab. Remember that this is a server-wide setting, though. You'll be telling Tableau not to do data caching for ANY of your data sources, so be careful. Generally, caching is a really good thing when it comes to making Tableau respond quickly, but in your case, it may not be.
Hope this helps!
Got the information from the client. They setup tableau with all the default settings. They have selected "Refresh less often". From the tableau conference one of the sessions indicated that caching was also dependent on two session variables: vizqlserver.session.expiry.timeout and wgserver.session.idle_limit. The client hasn't changed these settings so I'm assuming they are using the defaults of 2 and 4 hours.
When you say refresh less often means "keep the data indefinitely", would that be true for any period of time? If I open a workbook in tableau server that is using a live connection and hit refresh, close it, then open that same workbook a week later, would I see the same data until I hit refresh again?
We are experiencing a similar issue with Tableau Server. We have a live connection to a Vertica cluster with new data importing each day, and caching on our Tableau Sever set to "Refresh Less Often." It seems that once Tableau Server caches a dashboard under this setting, it does not overwrite the cached data upon refreshing the workbook or dashboard.
- User loads Dashboard A on 7/5/12 which shows all data up through 7/5/12.
- When the user returns the following day and loads Dashboard A, it only shows data up through 7/5/12 (due to "Refresh Less Often" setting).
- As a result, user clicks the 'Refresh data for this view' button and the data in Dashboard A refreshes and shows data up through 7/6/12 (great!).
- User closes or navigates away from the dashboard.
- User returns to the dashboard on the same day to see that it only shows data up through 7/5/12. The data retrieved as a result of the earlier refresh was not cached and the user must hit 'Refresh' again.
Any assistance on this would be appreciated. Thanks!