Tableau Dashboard Performance Series: Tip#39: Set Actions

First read this to understand my perspective on Sets, then read this to understand all sorts of cool things you can do with Set Actions.

Then, sprinkle your dashboard with some Set Actions. This is like a bit of salt or lemon on your dish, just a bit. Don’t overpower your dashboards with too many set actions or you are going to leave your consumers with a disgusted taste

Tableau Dashboard Performance Series: Tip#38: Viz in Tooltip

Viz in tooltips got a huge applause when it was launched at the TC a few years ago, but I tell you, I am not applauding the analysts who are now wanting to use this in every dashboard they build.

There is a specific purpose to building dashboards and that is to give your consumers ability to see things at a high level and yes, also have the ability to slice and dice the data using interactivity and filters.

Viz in Tooltip is a great way to get that next level of understanding that goes with the context but is it a good way to do adhoc analysis. That is the issue when my customers are asking for putting dashboards inside of Vizzes. I am not sure about that.

Any how, here is a way I think of using this features

So, this might a decent example of using Viz in Tooltip

But, this is NOT (as it requires too much thought processing from the consumer).

Tableau Dashboard Performance Series: Tip#36: Number of Data Sources

This raises many eyebrows. Why does the number of data sources impact my dashboard. And, I would say, it shouldn’t. And we have made many advancements where it might not.

However, in some of the older version prior to 10, we saw a direct co-relation between the number of data sources and the initial load time it took for a dashboard to load on the Tableau Server. If you are seeing that having a higher number of data sources is causing an issue, I would advise you to create dashboards that don’t use more than 3 data sources and compare it.

In any case, if you are combining more than 3 data sources for a single dashboard, I really think you should be using your enterprise data store (EDW or similar) to get the data so you aren’t combining data in real-time with data sources that are very different in terms of their technologies.

Another thing to consider is that Tableau makes separate connection to each one of the data sources so if you have 29 data sources to a database, Tableau might be doing some of the metadata work 29 times.

Tableau Dashboard Performance Series: Tip#35: Tableau Server Load

This happens to fall in the last category where there are certain items that are completely out of control for business teams.

However, having additional information hasn’t even hurt anyone. So, if time and again, you just need to ask your IT counterparts if the servers has enough hardware and it keeping up with the load of the users and the usage, they may appreciate that. In fact, you might need to prepare for some funding too so you can not only ask the right question but offer to help provide $ needed to ensure your success.

Tableau Dashboard Performance Series: Tip#34: Database Load

This happens to fall in the last category where there are certain items that are completely out of control for business teams.

However, having additional information hasn’t even hurt anyone. So, if time and again, you just need to ask your IT counterparts if the database that you are using to analyze your data has enough hardware to support the load on it.

In fact, often times, for enterprises, the data strategy involves setting up databases that support analytical loads. But, unfortunately, once these databases are setup, they are not often maintained how they should. Feel free to contact me if you would like to talk more about this