1 of 1 people found this helpful
With a live connection, Tableau has to continually re-query the database. So, if the query is complex or takes time to complete, then you could see some delay like this. Is it necessary to use a live connection rather than an extract? Is there any opportunity to optimize your database query?
While I can understand the need to query the data source and thus a delay would be created*, it doesn't make sense that it takes two separate passes/hovers on the mark to have the tooltip display.
It's not Custom SQL but I might be able to create another simplified and specific data source from the primary just for that sheet I suppose. It's not absolutely necessary for the connection to be live but due to the times this would be viewed (not often) a manually-executed extract in Desktop would be more prudent than publishing to the TS and unnecessarily using server resources.
However, it's the multi-pass behavior I find uncharacteristic.
*Thanks for that info, I didn't think it would query the other viz.
Is it really doing multiple passes or is it that the process gets sort of interrupted by the "Processing Request" dialog, requiring you to then hover over again? But that doesn't really make sense either, does it? You'd think that it would do it's query thing then show the viz-in-tooltip, rather than requiring you to hover over it again. Interesting...
I have definitely noticed that viz-in-tooltip has some delays, but I have not seen it do this. I'd certainly be interested to see if this occurs with an extracted data source.
One more question--what happens when you use a live connection and upload it to Tableau Server or Tableau Public?
Ask and ye shall receive...
Here it is, published to our Tableau Server using a Live data connection:
You'll notice that there is a delay but at least it doesn't require a double-hover. The downside is that there is no indication that something is happening.
I also republished the workbook but with an extract for the tooltip viz and the performance was immediate as one would expect.
Interesting. So I guess it's more of a performance issue than anything else.