Tableau Reviews

User interface is designed for ease of use for non-technical users. Users can pick up the product without attending training session. This is a plus.

I have only used it to demonstrate the ease of use to financial type users in the commercial market. It is used in academia as a simply learning aid for data visualization.

Integration with big data platform is a plus for any BI tool. They need to perform ETL/ELT operations with a direct connect to Hadoop ecosystem and RStudio for data quality tasks or offer a similar features.

Two years in academia and briefly with the State of Texas in a three month evaluation project.

No.

The free mapping component needs some enhancement for a better quality of geographic information, but it does connect with a ESRI mapping server for optimal data visualization of geographic information at an additional cost,

Never used it, but the training needs some online learning courses for Tableau administration instead of relying on partner relationships to provide this training.

I did not switch. I use QlikView, SAS Analytics, TIBCO Spotfire, and IBM Watson for college instructor roles.

I only used the desktop version for evaluation of the product, and the student version online in academia. It was simple to install, but I am not sure about the server configuration.

Pricing is fair for small business groups, but it also depends on the scalability that they need with the cartographic integration for better maps.

Great tool.

The ability to connect multiple data sources, build data extracts, and display said data in an automated, graphical, format is the key driving factor insuring I continue using Tableau. While there are plenty of other tools on the market, such as Report Builder or Crystal Reports, Tableau is the first I have used that allows for such wide spread data integration and presentation in a visibly pleasing format. Moreover, the data extract function of Tableau has hooked me into using their tool over any other. Specifically, the ease of extracting and automating report generation from these extracts.

Tableau has allowed us to build automated weekly dashboards that explain our organisation's pipeline. Moreover, these dashboards have resolved long standing time sinks which have freed up resources to focus on ever larger and more interesting BI projects. Additionally, we have used Tableau to increase the range and width of reports we are able to generate on a weekly basis.

Tableau development has an increasingly large learning curve. It is marketed as an upper management tool that anyone can dive into. However, trying to develop even simple tables within Tableau is an exercise in frustration and patience. The end results cannot be denied, but the path to getting there is not for the lighthearted.

I have used Tableau now for 2 years.

Tableau customer service has been incredible. Not only do they have an active community forum, but their account managers have been very pleasant to work with.

Out of five, I would rate technical support a solid 4.

I have used Report Builder and Crystal Reports. Switching wasn't really my decision, as the other tools used were at different organisations. Since then, I have tried to move back to other reporting tools, but found them lacking in functions I hadn't even realised I had come to rely on!

Setup of Tableau was the easiest of any reporting environment I have used.

We implemented Tableau through a vendor team who were helpful in getting us off the ground. That being said, any reporting tool is dependent upon the data set it connects to. As such, real value has only appeared from Tableau after long usage and learning of how to use its myriad of functions.

Stick with the development process, try a report over and over, and use Google to search out answers to those questions you think have no answer. Take it from me, if you can build it in Excel, then you can build it in Tableau. It just takes time and effort. Also, it may not look EXACTLY the same, but you can get it pretty close. In some cases even better.

Dynamic interactive visualisation and publishing to server for distribution are the most valuable features of this product.

Used on client projects, it was mainly helpful for visualizing proofs of concept for further implementations.

Data preparation and joining different data sources is still not very intuitive and could be improved.

I have used it for three years.

I had no issues with deployment, stability or scalability.

Customer service is very good, very responsive and helpful.

Initial setup was very straightforward, no issues encountered.

The pricing is complex and could be simplified.

Some very good and fancy visualisations are possible with "tricks" (not very obvious how to do it). It is very helpful to use the Tableau community to see if the visualisation one is looking for is possible and how to do it. There are also many ways to get to a result, so don't look for one perfect solution as long as you get what you want.

• Easy and intuitive chart creation
• Easy conversion between different chart types and crosstabs
• Easy map-based charting
• Built in geo coordinates for cities, states, countries- Easy-to-create fields with formulas
• Ability to connect so many kinds of data sources

• Now, the business decisions are "data driven" based on Tableau
• There are standard interactive reports/dashboards.
• And there is a dedicated data analyst role.

• Tableau can handle only one joined/denormalized table, e.g. students, classrooms, teachers.
• Sometimes I need to analyze the joined/denormalized table from multiple perspectives in one single workbook.
• Create analysis both for students, teachers and classrooms
• To use simple drag-and-drop is not enough to show
  
  • Average student age per classrooms or teachers because some students have classes multiple times in the same classroom
  • Average grades per teacher
• Sometimes I would like to analyse both student-classroom and teacher-student or classroom-student relations out of the original joined/denormalized table.
• I think the Qlik Sense approach is better for this very specific case.

I have been using it for nine months.

Tableau 8.3 did not scale properly.
I had four cores, but Tableu 8.3 was single-threaded. Tableau froze once in a fortnight, and without saving either *.tde or *.twb, they lost their sync.

I used and liked the documentation and user forum very much, and found there either a solution, a workaround or at least an explanation to my problems.

Initial setup was easy.

• We bought official basic and advanced Tableau trainings.
• My local Tableau instances (on my desktop and AWS instances) were installed by me.
• The central Tableau server was installed by the BI and administrator teams.

For a large company, the ROI is really fast.

Always buying the latest Tableau Desktop Professional is too expensive for an individual analyst/developer.

My team evaluated 50 visual analysis tools in 2014. I also was one of the key developers of Cygron Datascope.

Tableau was selected because it is the common platform for both data analysts and regular users. Both groups can use it. Of course, analysts can utilize more advanced techniques, but even an average user can understand charts and do basic things after 60 minutes of training.

Go for it. It is an excellent product for the majority of analyses. However, for complex reports and decision support cases, custom application development might be needed.

Ease of use, In-Memory data storage, native connectors for different DB’s and many more

We're a service based company and we most of the times get adhoc requests for implementing reporting. Since Tableau helps us create rich and meaningful visualizations in a short time frame, it’s helping us improve our business.

ETL functionality to be incorporated and Server to be improved in terms of including more features in Web Authoring, Quick steps in replacing data source connection credentials etc.

I’ve been using Tableau for 2.5 years.

• Tableau Desktop: No
• Tableau Server: Not meeting the hardware requirements
• Otherwise, deployment is smooth.

No. Just that hardware requirements need to be met.

Excellent

Excellent

I’ve used OBIEE. When compared to Tableau, visualizations are not visually appealing and I also had performance issues.

Straight Forward in both Tableau Desktop and Server.

In-house team

I cannot say a specific number, but lots of projects are using Tableau for their reporting solutions.

We’d bought 10 licenses initially and cost was discounted by $100 per license. No day-to-day cost but, we’ll need to pay maintenance of $500 per year.

Qlikview, Pentaho.

People should use Tableau because it is fast and visualizations will be rich.They can reduce the resource cost as reports can be done by a small team and does not require too much technical expertise.