Tableau Reviews

• Analytics
• Dashboarding
• Presentation
• Reporting

• Transitioned from static to dynamic reporting
• Transitioned from restricted to flexible visualizations

• Scheduling the reports as email to multiple users on daily basis preferably in Excel without creating user accounts for each user
  Establishing an effective connection from SAP BO universe to Tableau

I have used it for 3+ years.

I have not encountered any deployment, stability or scalability issues. I recommend filtering data at the source itself instead of bringing data into the tool and then applying filters.

Technical support is excellent. I hope they continue doing the same.

We previously used another solution. We switched to Tableau because, in my opinion, it has some of the best features available. It will take five years for other tools to catch up to where Tableau is right now.

Initial setup complexity was due to the organization's data structure, but it had nothing to do with the tool.

Implementation was in-house; we read through the guide.

It is expensive but worth it. I would prefer a lower license cost or an increase in the allowed # of users per license.

Buy it, implement it and stick with it for a sure and quick ROI.

The most valuable features of this product are:

• Easy-to-create dashboard
• Friendly user interface
• ShowMe
• Database connections

Users can generate reports by themselves, while IT people can focus on the database management.

It significantly reduced the time to prepare reports, from three days to three hours.

Add ETL function; add 3D graphics; add a keep-only filter because it is difficult to revert to the original data format; add more ShowMe options; include AI function.

I have used this solution for two years.

I have not encountered any deployment, stability or scalability issues.

I rate the level of customer service and technical support 9/10.

We evaluated Microsoft Excel and IBM Cognos: they are more time consuming, less efficient for generating reports, and more expensive.

Initial setup is straightforward, consisting of simple procedures for database connections and desktop setup.

An in-house team implemented it using self-learning materials.

Desktop Pro is US$ 1,999 each.

Define the main purpose of using Tableau, and in which aspects.

If you want the most beautiful dashboards, Tableau is the answer. If you want to shift your dashboarding/analysis development to your users, Tableau seems to be the best choice, as for the most part it’s quite easy to use.

It offers beautiful visualizations on the fly. New users will catch on to it quite fast for doing simple analysis. Creating complex objects can sometimes get quite tricky, but most of the things can be done very simply and quite faster compared to QlikView.

Tableau is moving fast. In fact, we see it as a leader in the data visualization market. We would like to see improvements in its enterprise capabilities.

It offers the Tableau server for deploying apps that can be shared and used by multiple users, but it needs further improvement to be able to support a large set of users in a big organization.

If you are planning to implement self-service BI in your organization, I see Tableau as the best fit, but you will need to find a good tool for ETL.

Also, if you are required to develop financial reports etc., Tableau might not help you much.

Nonetheless, you can run a Tableau solution without needing a lot of IT involvement.

Tableau needs some improvement in its organization-wide deployment capabilities.

Qlik Sense (a new tool by Qlik) tries to be like Tableau, but if you want something like Tableau, you better go for Tableau.

The best feature of Tableau is its simple GUI with drag-and-drop feature. It helps even a rookie create a great visualization. But for experts, it also provides flexibility of writing queries to fetch data. It’s easy-to-integrate feature - with almost all the databases - makes it a great value.

We have used Tableau for creating dashboards for our clients to help them visualize their data for developing business strategies. They can easily use the dashboard for targeting strengths and improving the areas of weakness.

The feature I would like to have is publication of a live dashboard on a webpage, so that dashboards can be incorporated in webpages. We can do this currently on Tableau public but because of data security, we need the dashboards to be private. But in private dashboards, we cannot publish it on webpages. Sisense provides this feature.

I have been using Tableau for the last two years, with the first year being for college assignments. I have exclusively used Tableau for creating dashboards for hotel clients.

I have not really encountered any deployment, stability or scalability issues.

I rate the level of customer service and technical support 8/10.

I have used QlikView, but I have always found Tableau simpler to use.

Initial setup was simple. I just had to install Tableau Desktop on my system.

An in-house team did the implementation. It’s easy to set up.

Pricing is steep.

If you have the budget, go for it. It’s the best money can get you.
I have loved working with Tableau for its simplicity and ability to handle large volumes of data. However, it’s a bit too expensive.

The feature we've found most valuable is Data Extract, which extracts a local copy of all required data in a columnar format store. It does in-memory processing which is lightening fast.

It placed the power of dashboards and scorecard development in the hands of business people, so there's less dependency on developers.

They need to make it more flexible for enterprise administration, e.g, more job scheduling flexibility, more robust permission control, and more comprehensive mapping service that is native and not dependent on a third party like Mapbox. They also need to develop more comprehensive DR and HA solutions.

I've been using it for over three years.

It's excellent for deployments and upgrades.

We have had no issues with its stability.

We have had no problems scaling it for our needs.

They have good customer service support, although they do not always solve the issues. Also, sometimes support takes too long to find the root cause or a solution to an issue.

We previously used Cognos, and Microsoft BI. We chose this due to user-friendly structure. There aren't too many components to manage and understand like in Cognos or Microsoft BI, etc.

The initial setup was straightforward -- very easy installation and upgrades cycle.

In-house - very easy to implement in-house, just follow the installation and upgrade guide check-lists and first try on test environment before doing a production installation or upgrade.

ROI for Tableau when compared to other BI tools we have is excellent.

Tableau has both core-based licencing (for higher number of consumers scenario) and subscription based licences (for limited users scenario) - chose appropriate licencing based on your estimate of number of users.

It's very user friendly and its self-service approach helps business users to develop dashboards in no time. The learning curve is very short - lot of learning resources available.

Still need to do some catch-up on enterprise administration and Mobile friendly reporting e.g Android App is not yet available - expected to be released 10.0.

Tableau releases frequent major releases three to four versions per year, and monthly patch fix releases, so plan a strategy that you want to follow. We are generally one to two releases behind so we can keep up with them, and at the same time leveraging all new exciting features the release.

Once you are comfortable with the product, building visualizations and dashboards is extremely quick.  I also have not seen a better geospatial drag and drop visualization tool out there yet.

It’s an excellent tool to quickly build visualizations supporting QA and data validation activities.

• Governed data discovery
• Collaboration
• Other enterprise features

We've used it for over two years.

We had no issues deploying it.

There have been no issues with the stability.

Older versions had trouble with performance when looking at larger datasets but it does not seem to be as much an issue now.

Sales support when we were first engaged with them was minimal.

There was no other solution in place.

It’s excellent for desktop analysis but make sure to include other tools in your evaluation if you are looking for enterprise support features.

• Visualization
• Data capacity

Where I'm working, we have many reports developed in Microsoft Excel to present results about the business. However, when we need to work a large volume of data, they are developed in Tableau because access to data from Oracle and managing large data volumes is easier than Excel. All the reports that we develop using Tableau are complimented by our directors, as the information is visualized well.

When we need to work with a large volume of data, we can create an extraction, validate data easily, and then present it to our users using Tableau Server or Tableau Reader.

I have difficulty working with many filters on the dashboards, and I'd like to see more options in the "Histories" section. QlikView makes better use of the dashboard filters.

We've used it for two years.

In some departments we chose to install Tableau Reader, but it's necessary to create a ticket to update the software for each new version. This process is not good as it disrupts our day-to-day functions.

I work with 4GB RAM and rarely I have a problem with it. My OS is 32 bits.

We've had no issues with scalability.

I always take support from Tableau's forums and communities.

We also looked at QlikView.

It's a great solution to present data, and our directors love to work with it.

It's a very good, flexible product, and it's easy to learn.

It's a new technology, so it's easy to get somebody up and running.

Scalability for large amounts of data needs improvement, as well as its performance.

From a scheduling perspective, if there is a sync up of the desktop dashboard into the server that we can publish as a web version, in an accessible way, that publishing scales and keeps on executing for hours. This can go on for eight to nine hours, but you have no indicator, you don't even see that it is processing. For example, there is no spinning wheel and all I see is a black screen.

The interface can be improved, in part because there is no indication that something is running or that it's processing. I would like to have some kind of indication that there is something processing on the interface.

Technical support could be faster or if they have any limitations of the product, they should openly communicate it. They could also just tell you that this product is intended for small volumes of data and may even suggest another solution.

We have been using the latest version of Tableau for several years.

As far as using low volumes of data, it is stable. If the data is too large then it becomes a problem.

From a data perspective, the problem with scalability is after a point in time, the data becomes very large. For example, there is a way to sync the data and bring it to the desktop, and if the data is going to be seven GB or more, that is a huge amount of data and creates a problem with Tableau.

Based on our customers, we have different licenses. We have approximately 15 different customers.

Technical support is fine, but it could be better. When we reached out with the large amounts of data, we were not provided with the correct solution.

We started with Tableau.

The initial setup was straightforward. There were no issues.

It's a very simple installation, it doesn't take a lot of time to deploy.

We did not use a consultant, we implemented ourselves.

We have a single person team for installation and maintenance.

We plan to continue using this solution and I can recommend it.

It's a good product but large volume data is an issue. Maybe people will have to work around it to make it smaller. It requires splitting up the data into smaller data files or we need to find another way from Tableau itself. They may have another scalable product, that can be used for large amounts of data.

I would rate this solution a seven out of ten.