Comparison of QlikView and Tableau

Differences of Tableau and QlikView:

Both applications are intended for a research and data analysis, but QlikView assumes approach of the developer, and Tableau analytical. Own ETL processor therefore it is possible to load and process any data is built in QlikView. Tableau requires already good data.

Data loading in both applications requires certain technical knowledge. In Tableau and QlikView it is possible to connect different data sources, such Excel, text files, databases. In Tableau of problems does not arise if it is "flat" tables, but for the rest it is necessary to be attentive and to monitor with cross-table relationships. Data loading happens in Tableau quicker and more simply (for the user) and it is one of the main differences.

In Tableau it is very easy to visualize data - the user can initially not know that he wants to see, but due to simplicity of treason of visualization, change of components, types of charts and filters can construct any diagrams. In QlikView the user should have rather good idea of what he wants to see before beginning to build the report – it takes bigger time.

If the user needs reports, calculation of a large number of indicators, then QlikView it is better to cope with this task, but at the same time more time and knowledge is required.

If the user has good data, studies more and goes deep into them, but does not do reports, needs fast change of cuts/indicators, then Tableau is an optimal product.

QlikView is optimal if:

1) Analysis of millions of lines of data;

2) Data need to be processed before loading;

3) Rather seldom there is a change of the reporting.

Tableau is optimal if:

1) Analysis of billions of lines of data;

2) Ready data for analytics;

3) Very often there is a change of the reporting.

Tableau minuses:

1) Parameters. It is impossible to use dynamic parameters, formulas for calculation of values, dynamically names of formulas, to change value of one parameter when changing another and td. It deprives of a possibility of creation of dashbord, comparisons of YTD without the choice of the period

2) It is impossible to compare the aggregated and not aggregated data. For example, record of a type [OrderDate] <is incorrect =max ([OrderDate]). Also, in IF a condition should be or aggregated, or there are no conditions and expression

3) Does not process hierarchical communications (except for dates).

4) There is no global search

5) Optimization of performance is a difficult task.

6) Additional resources of development. Tableau stakes on data visualization, forgetting about syntax of expressions and tp. Thus, a simple problem of demonstration of an object depending on parameter an easy problem in QlikView, but it is necessary application of alternate paths in Tableau.

7) There is no possibility of commenting

Tableau pluses:

1) Ease of implementation of comparison on the periods

2) Data visualization.

3) Groups and sets. The user can easily select selection whereas the user should write a trace to QlikView:

sum ({ Set1 <$ Year=:: Year, $ Month=:: Month> } [Amount]) - sum ({ Set2 <$ Year=:: Year, $ Month=:: Month> } [Amount]) that not each user will be able to write.

4) Cards – one of most strengths.

Practically all diagrams can be repeated in QlikView, but their setup takes a lot of time.

Advantages of Tableau over QlikView:

Data visualization. One of highlights which selects Tableau in crowd of BI-systems.

Development in the graphical interface, using a computer mouse. QlikView can offer nothing here, all fields should be selected and configured in dialogue properties and working panels have quite static model.

Cards are one of most strengths of Tableau. Display of the card as a background for creation of charts, without a possibility of detailing on regions and other additional layers offers QlikView a simulation opportunity. Tableau offers excellent functionality which includes constantly updated maps and the additional information (according to some license of the third parties), for example, the population (without what – or additional costs for the client). Though there is no decent detailed Russia map yet, there is an opportunity to load the.

Groups and sets. Tableau offers function of easy creation of sets "on the fly" using functions of addition, intersection, etc. In QlikView the user should understand syntax for writing of such sets:

sum({Set1<Year=$::Year, Month=$::Month>} [Amount]) - sum({Set2<Year=$::Year, Month=$::Month>} [Amount])

Creation of dynamic sets in QlikView is unavailable, requires creation of new structures and reset of the application.

Advantages of QlikView over Tableau:

Optimization of performance. During the work with QlikView the question of performance arises only during the work about very bigger a data set, but there are many manuals on its increase. But in Tableau this task is not simple. Optimization of SQL queries means presence of good technical knowledge at the user.

Additional resources of development. Tableau stakes on data visualization, forgetting about syntax of expressions and tp. Thus, a simple problem of demonstration of an object depending on parameter an easy problem in QlikView, but it is necessary application of alternate paths in Tableau.

Need for ETL. As well as any tool working with databases of Tableau needs a possibility of data translation for the purpose of their cleaning. In QlikView there is no this problem.

Conclusion:

Tableau is excellent Q&A the tool, developed generally for nontechnical users. However, creation of difficult reports nevertheless requires participation of IT specialists. Creating applications in QlikView usually requires participation of IT specialists, however at the exit more difficult and powerful tool kit for the analysis turns out.

<a rel="nofollow" href="http://biconsult.ru/products/tableau/qlikviewvstableau">More detailed, including comparison on functionality original of article</a>

</div>