Here's what I posted on an earlier associated posting:
Sorry
Researched both, but never actually used either one (?).
Sort of depends our friend’s use case doesn’t it?
Different business sectors, business sizes, and the sophistication of the BI champion involved (hopefully they have one in this case) have a lot to do with the deployment and adoption of any BI solution and its ultimate success in a business.
Hmmm …
Might this online resource help our BI puzzled friend?
CAUTION: This table may be somewhat biased towards Tableau! … but what on the net isn’t?
Some balancing factors in support of QlikView (from that same site):
- QlikView is certainly Enterprise ready with multi-server configurations.
- QlikView in the cloud offered by partners (Rosslyn being a prime example).
- ETL and data integration is very strong in QlikView - though very script driven rather than UI.
- I have seen articles re: integration with R in QlikView.
- Storytelling quite natural in QlikView - with tabs and navigation buttons.
- To my mind implementation time is very rapid in QlikView.
The ability to make data publicly available without the need to license each client and at a sensible price point (without the use of NPrinting or similar to push HTML or images to a web server) is somewhere I would like to see QlikView catch up though.
No mention of affordability for businesses or end user experience factored in, but from those perspectives, we’re learning about Information Builders’ BI solution …
Software Tester at a tech consulting company with 11-50 employees
Real User
Top 20
2014-05-20T14:51:27Z
May 20, 2014
A quick overview of Tableau:
- It offers business intelligence for dummies, review account, and partner programme
- It is going mainstream with the help of Google Drive
- It has gained the interest of Irish Life, who chooses Tableau over Qlikview
A quick overview of Qlikview:
- It is being used by Messier-Buggati-Dowty, NHL clinical research body, and Scottish Fire and Rescue
- It is reportedly being used to advance Business Intelligence resources, including feeding in data to the UK government website
- It has been remarked by analysts as easy to use for both IT professionals and non-IT users
I would say go with QlikView for your business intelligence needs for now.
Development times will be very different. Qlikview requires scripting to
lift data and then more scripting to create a QVD (data store) in which to
hold the data in memory. It also requires scripting and development to
build the dashboards. Essentially a lot of scripting by an experienced
developer to create those great looking dashboards.
Tableau is similar to Spotfire in being dimension free when it comes to
accessing data. In other words there is no need to script a data mart to
hold the data first. This makes it easier to mash up data from new sources
very quickly.
Tableau scores very highly on visualisation and presentation whereas
Qlikview perhaps scores better on data discovery. Overall though the
development times - and skills needed - will probably be higher with
Qlikview.
As ever it comes down to the principal need and you don't say what the
solution is intended to address - if it is pure visualisation of data then
I'd say the above is a strong consideration.
Business Analyst at a consultancy with 51-200 employees
Consultant
2014-05-20T07:14:33Z
May 20, 2014
I am not the correct person to explain the pricing part but definitely I can explain the functionality part.
Both Tableau and QlikView are great tools for visualization. I have used both the tools and find both the tools very easy to use.
Honestly I am more inclined towards Tableau and the reason are:
1) My clients send me their queries and they want some tools/charts to understand the data better. In this case I don't know what kind a chart should I draw. I play with dimensions , add more dimensions , flip axis, and switch between different types of charts, and this is why I love Tableau. You can discover new ways or say better ways in more efficient way in Tableau. The same can be done in QlikView but, if my clients wants to add one more extra dimension to the charts, I can do it in seconds in Tableau. I just need to drag and drop that dimension. QlikView has bit more rigid structure.
Why I love QlikView: In the case of Tableau, there are tricks involved, you need to learn those tricks but in the case of QlikView, everything is systematic. You have access over properties, expressions and all sort of options which is very systematic and you don't need to learn tricks for that.
Expression window is very cool in case of QlikView.
Lastly, What matters is the final outlook of the dashboard. I am impressed by Tableau Float and tile property in putting sheets in Dashboards. Very neat and impressive !!!
Architect at a insurance company with 10,001+ employees
Real User
2014-05-19T19:39:36Z
May 19, 2014
I can't address QlikView, but Tableau is a great tool for visual presentations. Very strong in graphics of all types and I *think *it has more currency/population than QlikView. Another tool that is comparable to Tableau is Spotfire which offers a more comprehensive suite of "input" / source connections, and more configuration options, than Tableau and has just as many graphical options if not more. I can't address comparable pricing as, I am sure you know, that can depend on timing (eg when the sales guy has to meet a quota at the end of the quarter) and volume and companion sales (Spotfire is offered by Tibco which offers many technology products).
I hope this helps ...
Solution Architect at a tech company with 51-200 employees
Consultant
2014-05-19T17:49:19Z
May 19, 2014
I agree with Ian that you would want to try something on the cloud, that will be cost effective. But if you still insist to with QlikView or Tableau.
I would recommend QlikView over Tableau as QlikView is more matured and has both Analytical and reporting Capabilities but Tableau has strong reporting capabilities and still lacks in analytical abilities. And also it does not have server architecture. But depends on how deep you want your analytics.
I can send more information which I did for a client of mine, you can contact me and I share the detailed document
If you are investigating new BI tools like Tableau and QlikView, then you most definitely should include Yellowfin in your evaluation. From a functionality perspective, they all produce pretty charts and dashboards, but for ease of use and collaboration features, Yellowfin stands out.
When you consider the fact that BI is designed to help us make better decisions, and that decisions now get made as part of a team or other collaborative effort in most organisations, then collaboration is crucial.
From a pricing perspective, it has been my perception that Tableau/QlikView pricing is similar, however Yellowfin as a subscription model, costs about the same as the support and maintenance alone of the other two. Yellowfin already has over a million end-users and was included for the first time on the Gartner Magic Quadrant for BI this year.
Here's what I posted on an earlier associated posting:
Sorry
Researched both, but never actually used either one (?).
Sort of depends our friend’s use case doesn’t it?
Different business sectors, business sizes, and the sophistication of the BI champion involved (hopefully they have one in this case) have a lot to do with the deployment and adoption of any BI solution and its ultimate success in a business.
Hmmm …
Might this online resource help our BI puzzled friend?
community.qlik.com
CAUTION: This table may be somewhat biased towards Tableau! … but what on the net isn’t?
Some balancing factors in support of QlikView (from that same site):
- QlikView is certainly Enterprise ready with multi-server configurations.
- QlikView in the cloud offered by partners (Rosslyn being a prime example).
- ETL and data integration is very strong in QlikView - though very script driven rather than UI.
- I have seen articles re: integration with R in QlikView.
- Storytelling quite natural in QlikView - with tabs and navigation buttons.
- To my mind implementation time is very rapid in QlikView.
The ability to make data publicly available without the need to license each client and at a sensible price point (without the use of NPrinting or similar to push HTML or images to a web server) is somewhere I would like to see QlikView catch up though.
No mention of affordability for businesses or end user experience factored in, but from those perspectives, we’re learning about Information Builders’ BI solution …
Hope that helps!
A quick overview of Tableau:
- It offers business intelligence for dummies, review account, and partner programme
- It is going mainstream with the help of Google Drive
- It has gained the interest of Irish Life, who chooses Tableau over Qlikview
A quick overview of Qlikview:
- It is being used by Messier-Buggati-Dowty, NHL clinical research body, and Scottish Fire and Rescue
- It is reportedly being used to advance Business Intelligence resources, including feeding in data to the UK government website
- It has been remarked by analysts as easy to use for both IT professionals and non-IT users
I would say go with QlikView for your business intelligence needs for now.
Take a look at Power BI in office 365. This will give approximately the same functions.
We have been testing it for one year and it works great and is cheap.
Development times will be very different. Qlikview requires scripting to
lift data and then more scripting to create a QVD (data store) in which to
hold the data in memory. It also requires scripting and development to
build the dashboards. Essentially a lot of scripting by an experienced
developer to create those great looking dashboards.
Tableau is similar to Spotfire in being dimension free when it comes to
accessing data. In other words there is no need to script a data mart to
hold the data first. This makes it easier to mash up data from new sources
very quickly.
Tableau scores very highly on visualisation and presentation whereas
Qlikview perhaps scores better on data discovery. Overall though the
development times - and skills needed - will probably be higher with
Qlikview.
As ever it comes down to the principal need and you don't say what the
solution is intended to address - if it is pure visualisation of data then
I'd say the above is a strong consideration.
I am not the correct person to explain the pricing part but definitely I can explain the functionality part.
Both Tableau and QlikView are great tools for visualization. I have used both the tools and find both the tools very easy to use.
Honestly I am more inclined towards Tableau and the reason are:
1) My clients send me their queries and they want some tools/charts to understand the data better. In this case I don't know what kind a chart should I draw. I play with dimensions , add more dimensions , flip axis, and switch between different types of charts, and this is why I love Tableau. You can discover new ways or say better ways in more efficient way in Tableau. The same can be done in QlikView but, if my clients wants to add one more extra dimension to the charts, I can do it in seconds in Tableau. I just need to drag and drop that dimension. QlikView has bit more rigid structure.
Why I love QlikView: In the case of Tableau, there are tricks involved, you need to learn those tricks but in the case of QlikView, everything is systematic. You have access over properties, expressions and all sort of options which is very systematic and you don't need to learn tricks for that.
Expression window is very cool in case of QlikView.
Lastly, What matters is the final outlook of the dashboard. I am impressed by Tableau Float and tile property in putting sheets in Dashboards. Very neat and impressive !!!
Hi I don’t have a current comparison.
My 2 cents:
QV is better for enterprise (or large dept. solutions).
Tableau is better for self-service / analysts.
I can't address QlikView, but Tableau is a great tool for visual presentations. Very strong in graphics of all types and I *think *it has more currency/population than QlikView. Another tool that is comparable to Tableau is Spotfire which offers a more comprehensive suite of "input" / source connections, and more configuration options, than Tableau and has just as many graphical options if not more. I can't address comparable pricing as, I am sure you know, that can depend on timing (eg when the sales guy has to meet a quota at the end of the quarter) and volume and companion sales (Spotfire is offered by Tibco which offers many technology products).
I hope this helps ...
I agree with Ian that you would want to try something on the cloud, that will be cost effective. But if you still insist to with QlikView or Tableau.
I would recommend QlikView over Tableau as QlikView is more matured and has both Analytical and reporting Capabilities but Tableau has strong reporting capabilities and still lacks in analytical abilities. And also it does not have server architecture. But depends on how deep you want your analytics.
I can send more information which I did for a client of mine, you can contact me and I share the detailed document
If you are investigating new BI tools like Tableau and QlikView, then you most definitely should include Yellowfin in your evaluation. From a functionality perspective, they all produce pretty charts and dashboards, but for ease of use and collaboration features, Yellowfin stands out.
When you consider the fact that BI is designed to help us make better decisions, and that decisions now get made as part of a team or other collaborative effort in most organisations, then collaboration is crucial.
From a pricing perspective, it has been my perception that Tableau/QlikView pricing is similar, however Yellowfin as a subscription model, costs about the same as the support and maintenance alone of the other two. Yellowfin already has over a million end-users and was included for the first time on the Gartner Magic Quadrant for BI this year.
This would be a popular question – I think a lot of people would be very interested in responses to this evaluation request!