Ok, so we all know they are different technologies but customers are often confused as to what the limitations might be with Tableau. Trying to compare visualisation tools is missing the point when it comes to Qlik products. Tableau used to have a perceived edge on pretty visualisations but with the release of Qlik Sense, that is a thing of the past. 


Apart from the obvious differences, i.e. Qlik does not require you to have your data staged in a DW or ODS to combine large and multiple datasets or that Qlik's in memory associative model gives users an unrivalled discovery experience, this blog, written by a Tableau expert, explains how to get the best performance from Tableau and essentially says ' don't do anything that Qlik does with ease'.


So if you have perfect data, a big DW team and you do not expect your business requirements to change much, go for Tableau if you want. For everyone else, Qlik is the answer.


Here is the blog:
http://www.interworks.com/blogs/bfair/2015/02/23/tableau-performance-checklist

Some of my favourite comments include:

• Keep analysis simple. Work with a subset of your data. Extract a sample if needed.
• Use extracts wherever possible to accelerate performance. Hide unused and confidential fields. Roll up data granularity by pre-aggregating or filtering. Break hierarchies to only visible dimensions.
• Limit blended calculations. They require sequentially querying multiple data sources and can be time-consuming. Where possible, create a view on the database server.
• Minimize the number of quick filters. Use dashboard filter actions where possible.
• Limit the number of worksheets on a dashboard. If you have more than four visualizations on a dashboard, strongly reconsider.
• Fix dashboard size relative to end-user consumption. Automatic sizing is less efficient than specifying dashboard size.

Thank you Tableau expert, perhaps it's time you changed to Qlik too.

Ben