We performed a comparison between Google Data Studio, QlikView, and Tableau based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Tableau, Oracle and others in Reporting."Data Studio integrates seamlessly with other Google products, and we can use it with other APIs if we like."
"The ability to design complex data models and equations."
"Valuable features include advanced integrated analysis and easy implementation."
"This has improved our organization by allowing people to see their data and develop visualizations themselves."
"The solution is free so that is a good feature."
"I find it favorable regarding speed of development, ease of building, and flexibility."
"I am impressed with the tool's scheduling mechanism, refresh mechanism, and different types of charts."
"The ability to integrate with a great variety of data sources."
"It enables us to configure various elements, such as dashboard settings, including factors like color schemes and other customization parameters."
"E-T-L, The Extract, Transform, and Loading capabilities of QlikView make it a highly sophisticated self-service business intelligence tool for developers and analysts."
"QlikView is one of the strongest tools, I would say. Also, it has a very vast capability to process the data"
"The language support is very good."
"The search feature: ability to see the related data."
"The most useful feature of QlikView for me is the QVD concept."
"We can scale it if we need to."
"Data transforming with scripting, and the associative model that lets users browse data in an easy way, are the most valuable features."
"The maps and colors and interface are all fantastic."
"Tableau has many good features. It is user-friendly, has a simple-to-use interface, and has a customizable dashboard."
"The solution is easy to use, flexible, our clients enjoy seeing the data on maps, and you do not need to be an expert in SQL to use it."
"One of the most valuable features of Tableau is that it's a visual analytics solution, not just a dashboarding solution. Compared to Power BI, which is a dashboarding solution, there are no limitations with Tableau. For example, when you add a chart or a map to Power BI, it has a 3,000-point limitation. When you try to track your whole vehicle on the map, you only see the first 3,000 rows on the map, and Power BI doesn't tell you which part of the data is shown on the map. But Tableau doesn't have any limitations, which means that you can see five million data points on a map. It starts the project by creating the visuals that directly converts to SQLs. In that way, all the components have no limitations. When we compared Tableau to Power BI, we also found Tableau to be more fancy. Fancy means you can create more visual graphics and more visual dashboards. With Power BI, this isn't so—it's just some tables and some simple charts together. Tableau is more for business users who want to analyze data. Tableau can directly connect the analytics systems, like R or Titan, and get the results in screen, so it's a good solution for analytics scientists. It has some predefined capabilities to understand the data."
"Tableau is easy to use. That's the first and most important thing. I not only provide consulting but I also train people to use it, so with its ease-of-use it's not as difficult for me to train executives and management staff, because they don't have the IT background, unlike when I'm using Python."
"We frequently utilize visualizations using maps and different objects, all with rich coloring options. And tooltips are absolutely essential for us. Tooltips, like the pop-up descriptions when you hover over some object or graph. Those tooltips in Tableau are great features."
"The ability to deploy is the added ability to centralise the Tableau repository for all Tableau Developers."
"Partner support is very good."
"There is a significant degree of sophistication required to compete with Tableau or Cognos."
"Stability and scalability an be improved for a full ten."
"The tool should come up with data modeling layer features that are present in other products like Power BI."
"There are issues with integration and I encountered limits and warnings, especially with my pivot table size."
"Panels are not as easy to use as other data extraction UIs."
"Insisting on forums, blogs and community outreach in communications, and posting videos on an established calendar would be useful."
"It's not yet a replacement for a complete BI tool."
"When you physically install a product on one machine instead of the cloud, you have a better visibility, best icon quality, etc.. It's more of an issue with how we are adapting to the transition. We are still in the early moments of using this tool, and we need to go deeper to discover some improvements."
"Though the initial setup phase is simple, when it comes to the integration with the custom systems, the configuration and the compatibility sometimes take some more time."
"Syntax editor needs some work, it's frustrating to have valid syntax being flagged as incorrect."
"They could improve the speed."
"If a user wanted to see something not included in the application the new object had to be created by a power user or developer because Qlik view's scripting has somewhat of a learning curve."
"This solution would be improved with the inclusion of a feature that would allow us to add a common library of (our) commands used in load scripts and expressions, so with a keyword, we would get a drop down to select the command we are looking for, as opposed to the generic help."
"Improvements are required in the hide and unhide functionality that falls under the layout container feature that has been used in my company in recent times."
"For me, it is important to have a mix, what is the "view" and what is the "sense", Qlik Sense. They have two tools, but for me it is important to have only one tool, which combines the functions that we have from one side and the other side."
"The pricing is high."
"In the cloud sometimes the performance is a little bit slow."
"Navigating through activities like cleansing, reshaping, and wrangling extensive or complicated datasets could prove challenging within the Tableau environment."
"Its integration with Microsoft products such as Teams should be improved."
"Provide additional enhancements in any business process: Operations, Marketing and Sales, Finance, Human Resources, Logistics, etc."
"Its documentation can be improved so that a user can get a good hands-on experience. Tableau is well documented, and on their website, there are a lot of tutorials that are available for free. I started my learning process through those tutorials, but there are certain loopholes in those tutorials, which only got filled through a couple of good YouTube channels that talk about Tableau. YouTube helped me a lot. So, the documentation could be better, I understand that it is evolving day by day, and with more usage, there would be more such documentation."
"Tableau's automatic insight could be improved. It has some predefined capabilities to understand the data, but I think they need more. Customers need more insight automatically from data—they don't want to discover them, they want to get the forecast automatically. The data preparation should also be improved because it's not easy. Tableau tries to focus on the business side, but the backend side has not improved much. They also have an ETS solution, but it's limited."
"I have noticed that Tableau is not very compatible with ClickHouse. There's no direct connection to ClickHouse; you have to set up an ODBC connection."
"The user story model is the most deceptive part of Tableau. It is a big marketing option, however, the reality is that it is not enough."
