Tableau Reviews

I primarily use the solution in order to utilize the graphs. It offers a good diversity of graphs and I can manage different data sets together with Excel. I can publish it for my manager, if, in the future, I'm going to use it at work. 

The solution offers good capabilities in terms of responding to my requirements. My dataset is so small and I don't need any complex graphs. It makes it very simple.

The solution is very stable.

The initial setup is quick and easy and you don't need special outside assistance to set everything up.

The integration with other program languages, like Python, needs to be better. I know the capability is there, however, there needs to be better integration. There needs to be integration for machine learning and AI. That would help data analysts and data scientists quite a bit.

I've only been using the solution for a few weeks at this point. I'm working on gaining some experience and familiarity with the product.

I've found the solution to be quite stable and reliable so far. I haven't used it long, however, I can't recall it crashing or freezing. I haven't experienced bugs or glitches. Its performance is good.

There might be about 20 people in our organization that use the solution.

I'm not sure if we will continue to use the product. Currently, I've only used it for a few weeks, and I'm learning it. However, our organization seems to like to work with Oracle. I'm not sure if we will focus on that or not in the future.

I've never used Oracle's technical support in the past. I can't speak to how well they help users with issues or how fast they respond.

I've worked a bit more with Power BI.

Our organization also works with Oracle's Analytics.

The installation was very, very easy. I didn't have any issues at all. It wasn't complex.

The deployment took less than 15 minutes. It was very fast and seamless.

I handled the implementation myself. I only had to download it onto my own PC.

Our company hasn't yet made a decision on the product in terms of long-term usage. I'm not sure what the licensing status is at this point.

We're just potential customers and end-users of the product. We don't have a business relationship with Tableau. I'm very new to the product and still really just testing it out to see how I could potentially work with it in the future.

I'm working with the latest version of the solution.

Overall, in my short time using the product, I've been largely happy with the results. I'd rate the product at an eight out of ten.

On-premises

The most valuable features are:

• Ease of setup
• Ability to create visualizations
• Level of interaction.

The users required no training after visualizations have been presented to them.

There are some areas where finding answers required asking specific individuals and searching through many emails. Tableau has allowed us to combine and visualize data from many entry points and provide users with a single source of consistent and reliable information.

While noted that the product is specifically designed for visualization, it would be the perfect tool if it had more ETL features.

My company has been researching a BI tool for the past year. We came across Tableau and have been using the public version for approximately six months.

There have not been any areas of instability, thus far. The identified areas were a result of a lack of knowledge.

Based on the analysis currently being done, the public version is sufficiently meeting our needs.

Technical support has been awesome. We met a partner based in Trinidad and they have been providing us with assistance as we need it.

This is our first visualization solution being used. Attempts were made on another platform, but setup and use of tool were a huge challenge for the team.

The initial setup was very straightforward. The team was able to follow the videos posted on the Tableau website and required no technical assistance from the Tableau team.

I am quite pleased that Tableau has now revised their pricing and licensing. The initial model was quite expensive but the current model allows you to scale up as you need to and it is far more attractive. The ability to license on a per user per month basis is now very affordable.

The team looked at Pentaho, Microsoft Power BI, and IBM Cognos. The members of the team who were exposed to aspects of the evaluation were far more receptive to Tableau than the others.

It is very important to do an evaluation of your users who will be interacting with the tool. Their technical abilities will determine if a cumbersome tool is suitable for them. Secondly, if you do not have the technical expertise to administer a product, then it may not be the solution for you. Some of the other tools require a high dependence on the vendor for administrative purposes.

The drag-and-drop interface and its flexibility are the product's most valuable features.

It requires only a one-time effort to design worksheets and dashboards. New data can be appended or a whole new set in the same data structure can be loaded to existing working files without much effort to obtain the same results.

I would like to see more Excel-like functionalities, perhaps, e.g. the countifs function. It is quite a hassle to code this using query language.

I have used Tableau for around one year.

Hassle-free deployment for desktop version.

Initial versions crashed when large data sets were loaded. Subsequent releases were more stable.

Technical support is excellent. Tableau consultants were eager to help.

We chose Tableau for its simplicity and ease of use.

For the desktop version, initial setup was straightforward.

The straightforward installation can be performed in-house.

A non-complicated licensing scheme exists for the desktop version. Buy, activate and use. Licensing was easily manageable with a license key that could be activated or deactivated on a system as required.

Try it out to see if it suits your organisational needs. To make the product work as desired, know how it works and implement workaround solutions if that is not readily available.

Data visualization: Simpler and cleaner charts, easier for users to perform self-service, not so steep learning curve for non-technical users; good integration to big data Hadoop and predictive analysis, well integrated with other ETL tools. Less-technical maintenance cost compared to QlikView, which requires the developer to do more scripting.

It is easier for users to do self-servicing; simpler, cleaner and story-telling charts; and requires less lead-time to develop charts/dashboard integration with predictive analytics and big data platform Hadoop.

Enhance standard reporting like QlikView (scheduled reports, notifications etc.); for MNCs, the server version license is not cheap; and row-level security: every user needs a DB account, which can give a hacker more opportunity to attack via more DB accounts.

I have used Tableau for two years.

I had a deployment issue: No version control means you can't roll back to earlier versions once overwritten/published.

I rate technical support 8/10.

Initial setup was straightforward.

An in-house team implemented Tableau.

Tableau seems to have easier user acceptance than QlikView because of the simpler charts and big data integration, increasing the possibility of helping an organization transform from reactive analysis to predictive analysis.

Server versions are not cheap and pretty similar for both Tableau and QlikView in terms of price. I don't see a big difference; it really depends on your organization's need.

I also evaluated MS BI and QlikView. Compared with MS BI, I find Tableau and QlikView have stronger visualization; intuitive data insights; less development lead time - MS BI requires creating OLAP cubes, which takes more time; clearer and simpler charts; and intuitive data mapping/insights.

If you have more developers/technical people and want to do more standard reporting without Hadoop, go for QlikView; if you have more business users with some SQL knowledge and would like to do predictive analytics, and integration with big data platform Hadoop, go for Tableau.

• Flexibility producing visualizations
• Scalability

Anything and everything becomes fact-driven; we don't do a lot by gut feeling.

ETL functionality is limited, which is both a strength & weakness. It would be nice to have Alteryx & Tableau as a package, but I believe Tableau have deliberately stayed out of the "deep" ETL capabilities to "stick to the knitting", which they have done very well.

I have been using it for eight years.

Any issues we have encountered have been related to data preparation rather than the tool itself.

Technical support is excellent.

I have historically developed using SAP BusinessObjects and IBM Cognos for visualization and various tools for ETL. I have trialed Qlik and Power BI, but this has a much higher level of maturity at this stage.

Initial setup was significantly easier than other products I have used.

An in-house team implemented it. Your investment needs to be in data preparation, then the implementation of any of these analytics tools is much easier. Typically, I spend between 70 & 90% of project effort on data not the tool. If data is well prepared, the Tableau development is very quick and best handled by the business analysts, rather than any tech personnel.

To get the best from Tableau you need:

• Data preparation suitable for analytics applications. (This is not Tableau specific, the same is required for pretty much all analytics apps.)
• People bouncing off each other to get the creative process going. Consider internal show & tells and take advantage of local user groups
• Subscribe to "Viz of the Day” to get exposure to as many viz's as possible
• Tableau is (I believe) the best tool for data visualization. Equally consider investing n the best tools for data preparation, such as Alteryx. The combination of best data prep with best analytics capabilities is MUCH more powerful than either without the other.

The most valuable feature is the ease of generating management reports on demand, and ease of generating incremental extracts live or work very quickly.

The integration with R for more complex algorithms in analytical data is also nice.

We use it to generate intelligence reports core business of insurance we develop. It is also part of the business intelligence tools we recommend.

Part graphical gauges compliance does not include the Balance Score Card style, however you can develop these graphics, another shortcoming in not having mondrian engines.

2 years

We've had no issues with deployment.

We've had no issues with stability.

We've had no issues with scalability.

Easy setup and intuitive drag and drop functionality. Easy connection to a range of different data sources. Range of visualisation models, constantly extending with new releases. Dashboards and story-telling.

It has allowed a shift from IT-centric enterprise reporting to business-centered development of ad-hoc and enterprise reporting, in partnership with IT. This brings significant extra agility to the organisation and a model of greater co-operation between business units and IT department.

As with all products there are many areas that can be improved. Tableau actively encourages suggestions from its user community, allowing for voting on what features to include it future releases. http://community.tableausoftware.com/community/idea

3 years, starting with Tableau 6.0.

No significant deployment issues. With a sufficiently resourced infrastructure (CPU/RAM/Storage) the product is easily deployed. Tableau helps with the necessary specifications.

It is a mature and very stable product.

Scalability is very good, especially with release of Tableau 8 which brought 64-bit and multi-threading. Extends to hundreds of users on a single server in my organisation without any issues and has capability to include clusters of servers for larger organisations.

Customer Service: Very good. Very little need to deal with them on an ongoing basis due to the robustness of the product but on the occasional time we need some help they are very responsive.Technical Support: Initially very good with strong technical support easily reached. As the Tableau user-base has grown quickly there are more formalities to reaching support now but still top-quartile. Again little need to lean on them due to the stability of the product and strong online documentation and forum support.

Oracle Discoverer. Switched because we needed to move to a partnership model between IT and Business units. While Discoverer allowed for power users in the business to author reports its metadata layer and underlying database technology required more intensive IT support. Tableau enables the business user while giving more agility to work together to deliver ranges of enterprise solutions.

Straightforward. Get a good server and provision it according to Tableau’s technical advice, install, and you’re away.

Mainly in-house, some support from Tableau themselves and also a local Tableau partner. Expertise of partners not great at the time in Europe but has matured considerably over the last few years.

Commercially sensitive.

Commercially sensitive.

Sas Microsoft SSRS Qliktech Oracle OBIEE Microstrategy

Assess your own strengths and create a preferred architecture. Then see if Tableau fits some of your needs. For anything significant in scale you will need a robust underlying data architecture, it won’t do all of your ETL. While it is possible to create and deploy artifacts very quickly without formal training, it is worth sourcing some to help you leverage the best features of the product.