What is the advantage of qlikview over tableau?

[#1]

what we can do in qlikview but not in tableau can any one elaborate this

Thanks

[#2]

http://www.trustradius.com/compare-products/qlikview/tableau

It is a matter of opinion many threads exist and their are many pros and cons for both products.  You need to as what will Qlik be able to do vs what will Tableau be able to do.  If you look to the future products in development you will see Qlik comes out ahead of Tableau, if you look at the here and now most would say Tableau out performs Qlik.

[MK_QSL]

Tableau cannot compress data , unable to handle data volume that Qlikview Can handle.

Tableau is a great product, as is Qlikview, but which is the better for your client depends on their needs. Tableau is easier to use, more intuitive and quicker to learn. Qlikview has more powerful/flexible reporting capabilities than Tableau

You need QlikView if you:

1. analyze millions of data,

2. need ETL tools,

3. employ IT specialist,

4. quite often modify analysis.

You need Tableau if you:

1. analyze billions of data

2. already have ETL tools

3. employ IT specialist

4. very often modify analysis

Tableau require seperate ETL tool but Qliview do not require any seperate ETL tool.

QV can produce better reports but it takes more skill and time to develop than with Tableau.

If you’re working in a more structured environment with relatively generous deadlines, supported by a good technical team then QV could be the correct product for you as it’s slightly stronger for reporting.

Qlikview v/s Tableau

[sudeepkm]

There can be many differences found between two products. Better to categorized the features and then compare.

From experience I think these are the couple of things not available in Tableau but available in QlikView.

You can check and make sure.

1. Extension objects for third party visualization

2. Column level data reduction based on users login (in QlikView we have Section Access)

3. Does not support connectivity with XML data sources.

4. Does not support pagination (i think this is not available in QlikView too)

5. bookmarks

6. Does not provide a Report Selection drop down panel like QlikView

some of the good things in Tableau are

1. It has native driver for Big Data, sales force and Google Analytics

2. It does not have a data handle limitation like QlikView

3. It provides suggestions of visualization charts according to the dimension and measures. (this is really  a good feature not available in QlikView)

4. It has a free viewer software known as Tableau Reader to view workbooks created in Tableau Desktop.

[marksmunich]

I would say both are the among the best BI tools. My suggestion prepare a list of your requirements, which makes it easier to make a decision, comparing the features in general doesnt make sense. Every BI tool has some hidden power.

[hic]

I am biased - I work for Qlik - but if I try to be objective, I would say that

• Tableau is an excellent visualization tool. QlikView 11 has some limitations in this area.
• Tableau is easy to learn. QlikView 11 needs an application developer who can understand data modelling.
• QlikView can handle any data, also unprepared, and merge data from different sources. Tableau needs prepared data (read ETL tool).
• QlikView can manage much more complex calculations. You soon hit the limit for what Tableau can do.

So, if you compare them in a test, Tableau may win if the test is easy. But QlikView will win if it is difficult.  

HIC

[jaimeaguilar]

Hi,

I really love QlikView, but I will also try to be objective, so according to my experience I can tell you this:

• In favor of Tableau I have to say that  is an outstanding vizualization tool. When you're working in the front-end some tasks like creating charts may take you less clicks than if you try to do the same in QlikView.
• However, Tableau needs the information as clean as possible in order to present data in dashboards. So in most cases is better to have a Datawarehouse ready to connect or make some transformations in your DB.
• QlikView has their own data file for storage (QVD), which compresses data as 10 times of the original size. There is no equivalent to QVD in Tableau
• In QlikView you can handle heavy scripting transformations. So you can go from extraction through data visualization with a single tool. Like I said, Tableau doesn't have a scripting engine, so most of the times you need help from other tools.
• Set Analysis can be very powerful to make calculations on the fly, although syntaxis could be a little tricky.
• Because Tableau doesn't have a QVD equivalent, you're limited by the DBMS in terms of response times.
• Also as an additional opinion, some time ago I was involved in a proof of concept against Tableau. We needed to connect to Sybase. The problem was that the database rejected connection after several thousand of rows. In total we had to extract about 60 million rows. The solution was to store data in QVDs per month so the connection didn't die. At the end, Tableau persons couldn't connect to this data because Tableau can store natively data like QlikView can do and because connection to database was unstable. In this case, Having their own data structure was a killer feature,

regards

[marksmunich]

I Agree with Henric Cronström Tableau is best at Visualization and Easy to Learn, But incase of Qlikview one need to be good at data modelling and also performing the ETL with Qlikview, but Both has its own adavantages.

[#9]

Jaime, thanks for the analysis, it was helpful. I've never used QV, but I am a heavy user of Tableau. Just wanted to mention possible misconceptions about Tableau.

Tableau also has it's own data storage file, namely tde files that are extractions of the data, which you can apply filters and aggregations to at the time of extraction. This can greatly reduce the size of files. Tableau isn't as much in need of 'compression' because they are not trying to do everything in memory. So while you're right this isn't an exact equivalent, it is filling a similar need, just doing it the way that is best for Tableau's way of handling data.

Tableau does have a 'scripting' ability. We can join tables, UNION tables, etc. We can write custom SQL codes using most of the common functions. So we can transform data as we connect to it. We can also make separate data connections to different tables and then 'blend' these. But again you're right, we don't have built-in ETL tools as it sounds like QV does.

Cheers,

--Shawn

[#10]

Shawn Wallwork

Shawn, please help me.

You could explain for me some actions positive and negative from Tableau, like TDE file, do I dont have script in tableau? and others points.

Tks