Try our new research platform with insights from 80,000+ expert users
PeerSpot user
Principal Business Intelligence Analyst at a logistics company with 1,001-5,000 employees
Vendor
It starts with numbers, and then represents them as shapes.

What is most valuable?

There are so many smart features baked into this product, it's hard to even rank them. I think what makes Tableau stand out over other software I've used is that it doesn't start with a visualization, then pump numbers into it: It starts with numbers, and then represents them as shapes on a canvas. The result is more akin to an artist painting on a canvas using numbers as the brushes and colors. As a result, it is the flexibility of the mark types, and how they interact with data types, that make this product stand out. Someone who wants to create a visualization need only imagine the intended output, then use the numbers to create the marks in that output.

A non-trivial example is that a number can be considered continuous or discrete, depending on the context. In some cases, you need to use the same number both ways in the same visualization (histogram, anyone?). The flexibility to specify how a number is interpreted in terms of how an axis/mark will be generated is visualization at a more fundamental level. It is a completely different experience than pointing Excel at a highly manipulated table to generate an inflexibly structured chart type.

How has it helped my organization?

The use case has been different from one organization to another. In most cases, the initial buy-in and value-add is at the analyst level. The freedom to calculate, then derive, then iterate - that never-ending cycle every analyst out there knows well - to do that, do it quickly, and in a way that is remarkably beautiful, is every analyst's wet dream. Even if an analyst never shares visualizations they create during the course of a project, the tool makes them better and faster at deriving insights of their own by virtue of everything data visualization is meant to do for humans - improve understanding.

For organizations that have the capital to take it further, beginning to push out the interactivity, reports, and resulting insights up the ladders, or out the branches of the organization, with buy-in to the more-expensive server options - well, those organizations wield a much greater force. The ability for decision makers whose decisions affect many lives, higher in an organization, or the net effect of decision makers who make thousands of small decisions every day - Tableau, used well, makes it easier to make higher quality decisions faster. The same can be said of any technology used well, to be fair, but Tableau’s beauty and speed to insight is unmatched.

In my case, I have also used Tableau as a report prototyping platform. Designing and implementing is so fast in Tableau, when working with business stakeholders who may not know the specifics of what they want, and will ultimately be using whatever reporting platform their corporate standard is on - Tableau is great for iterating through version after version, change after change, until a report is built that is exactly what the business needs. Then, specific requirements can be written for a report builder using that corporate technology - which is invariably slower to iterate on. By moving the prototyping and proof of concept to Tableau, the development hours and agile lifecycle can be decimated.

What needs improvement?

Connectivity seems to be a sticky point, but it's also a hard nut to crack at the level that I would love to see. Tableau is fast, razor sharp on the whole - WHEN you use an extract. The problem is querying the data to fill the extract is only as fast as the source system. The result is that when you start working with large volumes of data, you often must start finding creative ways to improve the performance of your query. Here's where it gets tricky. I almost exclusively use SQL Server as a source. When I want to create custom data for an analysis (or some ongoing report with complexity), I have the latitude to write custom SQL. The problem is that in order for Tableau to retrieve metadata, the query sent to the server arrives as a subquery like:

SELECT * from ([your custom SQL here]) x

Because of this, I can't use a host of very useful T-SQL techniques that improve query performance or clarity. No CTEs, no temp tables, etc. In some organizations, the argument is that if you want that kind of complexity, wrap it up in a stored procedure and call the procedure (which, yes, you can call sprocs in Tableau), but that comes with its own disadvantages, which I won't get into too much here. But that is not to mention not all report writers or analysts have the privileges to create or alter sprocs on a server within their organization.

In any case, depending on how much control you have over your database as a Tableau user, as well as the nature of the data you are pulling, you may find yourself having to be very creative just to get data TO tableau to create larger extracts.

For how long have I used the solution?

I started using Tableau in version 7, around 2012.

Buyer's Guide
Tableau
March 2025
Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.

What was my experience with deployment of the solution?

Desktop deployment is a cinch. Server, I had no involvement with setting up.

How are customer service and support?

The user community is extremely vibrant and engaged, especially for how (relatively) young the product is, so I have only had two occasions to call support. In both cases, they were resoundingly helpful and responsive.

Which solution did I use previously and why did I switch?

Back in 2012, we evaluated it against QlikView and MicroStrategy. MicroStrategy was more complex than our organization needed, and Tableau won out on ease of use and feature set, but I don't really remember the grittier details.

How was the initial setup?

Initial setup was simple and fast for both Desktop and Server, but, as I mentioned, I was not involved in Server setup.

What about the implementation team?

In 2012, we used an in-house team. I was not deeply involved at the time, so I don't have much implementation advice. For a larger organization, Tableau has created a consulting arm specifically for implementation, and having read a few of the white papers put out by them, I would highly recommend using them for a large implementation.

What was our ROI?

ROI can only be attained by use, so the ROI will be a function of adoption, not features of the product. Make sure you have the culture and an execution strategy to get people engaged and using it. Compared to other BI software, it's very easy to use, but not everyone will start using it just because there is a new icon on their desktop. Figure out adoption. Focus on it.

If people are using it, the ROI will be there, but if you spend 6-7 figures on an enterprise feature set and nobody uses it, it will have been wasted.

For the prototyping situation described earlier - one complex dashboard built from scratch then implemented in SSRS - the saved development time alone paid for the Desktop license.

What other advice do I have?

This is a visualization software. Make sure you are looking at total cost of ownership in the context of other BI infrastructure that is still needed to get good ROI. Management of data at an enterprise level is more than just visualization, and if all of those things are in place, this product shines. If you have dirty data, slow resources, governance problems, etc., this software is not designed to solve those problems, and those problems will stunt the usefulness you get out of Tableau.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user158718 - PeerSpot reviewer
Sr. Tableau Architect at a financial services firm with 1,001-5,000 employees
Real User
Valuable: Actions, Paramaters, Maps. Needs Improvement: Dashboard Version Control, Report Bursting

What is most valuable?

Actions, Story Dashboard, Parameters, maps

How has it helped my organization?

Self service tool and ease of implementation

What needs improvement?

Dashboard Version Control, Report Bursting, More capabilities on maps.

For how long have I used the solution?

I'm currently using Tableau Desktop and Server 8.2. I've been using Tableau for 7 years.

What was my experience with deployment of the solution?

No issues with deployment.

What do I think about the stability of the solution?

Sometimes have issues with stability which are dependent on network bandwidth, latency and user logon from multiple browsers

What do I think about the scalability of the solution?

No issues with scalability.

How are customer service and technical support?

Customer Service:

3.5 (1-5 5 Being highest)

Technical Support:

3.5 (1-5 5 Being highest)

Which solution did I use previously and why did I switch?

Business Objects. I switched to Tableau because of self service capabilities and quick turnaround on dashboard development.

What about the implementation team?

In house (I installed and configured server set up)

What was our ROI?

4 (1-5 5 being highest) Financials can’t be disclosed.

What's my experience with pricing, setup cost, and licensing?

$60K

What other advice do I have?

Best Visualization and analytics tool

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Tableau
March 2025
Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
AnupGupta - PeerSpot reviewer
Vice President at a financial services firm with 10,001+ employees
Real User
Top 10
Good visualizations and good dashboards with a nice look and feel
Pros and Cons
  • "It's easy to use."
  • "If I have to develop any, for example, pie charts, I can develop them just fine. However, if I have to develop a donut chart, that I cannot do it in a simple way. There are tricks that I need to use if I have to design a donut chart. It should be more flexible and provide more visualization options."

What is our primary use case?

We use it for internal monitoring purposes.

What is most valuable?

I like Tableau a lot as its visualizations are great; there's no doubt about it. It's easy to use. 

The look and feel and features are very good. Dashboarding is very good.

The product has been stable. 

What needs improvement?

While my experience has been mostly positive, there are certain limitations, as every tool has.

If I have to develop any, for example, pie charts, I can develop them just fine. However, if I have to develop a donut chart, that I cannot do it in a simple way. There are tricks that I need to use if I have to design a donut chart. It should be more flexible and provide more visualization options.

It does not provide detailed reporting like other reporting tools such as Microstrategy or Cognos, or other enterprise reporting solutions.

If they could provide better reporting as well as visualization, it would be a perfect product.

Pricing is a major thing. If someone has to use it within an organization, it is not that cost-effective, especially when a competitor like Power BI or some other reporting tool comes almost free along with their cloud solution. If someone is opting for any cloud solution, any cloud platform, especially if I talk about Microsoft, they will give you Power BI almost free of cost, or at a minimal cost. In such scenarios, people would prefer using Power BI or a similar kind of tool rather than using Tableau. That is a major concern which Tableau should look into.

For how long have I used the solution?

I haven't been using it continuously, however, I started using Tableau around six years back. Since then, there have been two projects in which I worked on Tableau. I did work with it in 2021.

What do I think about the stability of the solution?

The stability has been good. there are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

What do I think about the scalability of the solution?

I'm not managing any scaling aspects. I'm basically from the development team. Every company has its own scaling goals. In my company, I don't really follow that aspect.

I can't say how widely used it is in my organization. When we deploy a tool, there are different teams. There are different stakeholders who are actually using it. I manage my team. I know about only my team, not other teams.

How was the initial setup?

I'm not part of that team that manages the setup. I cannot comment on that.

What was our ROI?

As far as ROI goes, I'm not directly aware of it, however, likely you can Google statistics. 

What's my experience with pricing, setup cost, and licensing?

The pricing can't compete with Microsoft, for example, which basically gives their BI product away for free to those that purchase cloud products.

Which other solutions did I evaluate?

I'm also aware of solutions such as Microsoft BI, which is bundled into Microsoft Cloud products. It makes it less expensive for users if they are already heavily using Microsoft.

What other advice do I have?

I'm a customer and an end-user.

I'd rate the solution at an eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Tech Lead at MindTree
Real User
There's no intermediate semantic layer, so the learning curve isn't as steep
Pros and Cons
  • "Tableau is an advanced specialized tool. One of the best features I've seen is the lack of an intermediate semantic layer. I think that's an advantage compared to any other tool like BusinessObjects or Power BI, which are Tableau's biggest competitors."
  • "Tableau support could be improved."

What is our primary use case?

We have Tableau installed in a massive environment. The Tableau sector is on a seven-cluster node, including one with two nodes for high availability. In our initial setup, Tableau was deployed across the entire infrastructure, so that's more than a hundred sites and around 30,000 active users, and each site has several projects, too. We have around 11,000 workbooks in total.

The maintenance of the entire infrastructure is done on-premises, including user management, authentication, authorization, permissions, and publication. We are constantly doing these tasks, including the SSL certificate renewals. 

What is most valuable?

Tableau is an advanced specialized tool. One of the best features I've seen is the lack of an intermediate semantic layer. I think that's an advantage compared to any other tool like BusinessObjects or Power BI, which are Tableau's biggest competitors. All of these have semantic layering, so the learning curve is high. Users have to understand the data model and the relationships, but Tableau has no data model, so you only need to know the relationships of the direct inquiry to build a report. 

For how long have I used the solution?

I've been using Tableau for about six or seven years.

What do I think about the stability of the solution?

Tableau is stable, and I believe stability is essential. Our infrastructure has been set up right. The last two updates have had very few bugs, so stability-wise, it is excellent. However, performance is something we need to investigate further. It's hard to say whether performance problems are on the Tableau side or an issue with the infrastructure or the data sources. If there is a performance issue, we can't identify precisely where the problem is. 

What do I think about the scalability of the solution?

The scalability is good. We already have some help from professional services, and we've conducted an analysis showing that the number of users will be increasing every year.

How are customer service and support?

Tableau support could be improved.

Which solution did I use previously and why did I switch?

I've worked with SAP BusinessObjects. Tableau is a visualization tool built into the infrastructure for doing analysis. That's Tableau's focus. BusinessObjects is for doing analysis of some data and then sharing it on the server. 

BusinessObjects is an enterprise tool that needs an extensive infrastructure. It requires a proper IT team to configure the semantic layer and the universal support and then build the report. And the most significant advantage enterprise tools have is pixel-perfect reporting. You can create a pixel-perfect report and share it as a PDF or Excel file with the same format. Tableau is more or less a self-service analytics tool, so we do not have those kinds of features. There are a good amount of differences between these two.

How was the initial setup?

Setting up Tableau is straightforward, and I don't think it took long. It took maybe a day or two for the installation and migration and all that. However, the planning took some time because we worked with professional services. Planning took maybe 40 hours. Tableau requires a good deal of maintenance. We have a team of about five or six people for the administration.

What about the implementation team?

We had professional services to help us.

What's my experience with pricing, setup cost, and licensing?

SAP and Tableau have different pricing models. Their code-based license is around $13 to $15 per year. I don't think Tableau has a code-based licensing model at all, so those enterprise tools are on the higher side.But on the other hand, Power BI is on the cheaper side compared to Tableau. Power BI is much more affordable and also good.

What other advice do I have?

I rate Tableau eight out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Director Consultoria at tecnoscala consulting
Real User
Easy to set up and simple to use with good dashboards
Pros and Cons
  • "It's very easy to use and users don't need any IT support to access it as the information is right there."
  • "The solution needs to improve its integration capabilities."

What is our primary use case?

SAP BW , TABLEAU Server an TABLEAU desktop, the Info from SAP were downloaded using SAP Data services and ABAPin a very large Steel Makin company in Latin America

How has it helped my organization?

Better an accuracy info every morning for decision takers regarding sales production and Customers Financial situation 

What is most valuable?

They were considered the gold standard for dashboard development. However, many people also have SAP.

The initial setup is very easy.

It's very easy to use and users don't need any IT support to access it as the information is right there. 

What needs improvement?

There were a lot of dashboards everywhere in the organization, however, when the company wanted to get the operational databases they were not connected.

The solution needs to improve its integration capabilities.

The performance and security could be better.

Many people saw Tableau as a silver bullet and it isn't. It's good for small things, however, not for an institutional way of doing things.

I'd like to see better integration with SAP.

I'd like an integrated ETL or some sort of data preparation capabilities. 

For how long have I used the solution?

We've used the solution since 2013.

What do I think about the stability of the solution?

The solution is stable.

In the past, you couldn't do a full query. You could do the right query or the left query but not the full query. They fixed that n 2016. 

Also, there was another problem in that their selling approach was very aggressive and they were selling to sales directors. However, the problem is that after that you need the Tableau server. You need the deployment of the Tableau server and you have your dashboard. You needed IT buy-in. In order that them to be able to be seen in all the organizations, or even outside your organization, you need to get the Tableau server. With that in mind, companies must have IT people or training in the Tableau server, and then the dashboard is just developed in the desktop so you can upload them to the server. With all of that comes a lot of issues around security, modelization, and performance theses issues were not approached or considered in any by the users 

What do I think about the scalability of the solution?

Scalable in the sense of a very good performance in te Tableau Server , nevertheless the info must be prepared or downloaded in a very well defined DataWarehouse

How are customer service and support?

We had a lot of trouble with Tableau at the beginning. There were issues that nobody had dealt with in the past.

There was an issue that was open for about two months. They couldn't reach a resolution. We started the Tableau server in an English version server, however, it was decided to install the Spanish version instead. We defined success criteria for our developments, our systems. In the analysis and the scope of work, we decided that every Tableau dashboard or whatever was going to have an acceptable loading time of six to a maximum of eight seconds. The problem was that it took 30 to 60 seconds. Technicians from Tableau, from Brazil, from the USA, came and looked at it. In the end, it was the Spanish version that was causing performance issues, and therefore we had to install the English version again.

They had the Portuguese, French, or Spanish versions behind in terms of updating all their software. That was the problem. There was a bug in the Spanish version that in the  English version didn't exist.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I'm also familiar with Power BI, SAP, and QlikView as well as Snowflake

How was the initial setup?

The initial setup is easy. You can install it on your computer and you can start to do a lot of dashboards. They have a gateway for many databases and you can get to the information in a very easy way. 

The thing is if you don't provide it with a very good ETL design you have the problem that all the fields are going to be dashboards. That's pretty common. Many organizations have a kind of operational database. With specialized databases. It's updated daily. The information is validated and confirmed and authorized. Whatever you do with Tableau is your problem. They install Tableau in that new server and the users go to that information. 

They make a copy of the transactional databases. They put it there and the users start to work. It's very easy.

In terms of deployment, for the desktop, you can have a visualization of information and you can get copies of the data on your personal computer. That can happen in minutes. It takes minutes or maybe half an hour to get going.

The problem is that you have to have some training. The training is going to take one week or so. In another week or two weeks, although you are not an expert yet, you start to understand Tableau. You don't have to be technical. If you understand Excel well, you will find Tableau pretty straightforward. 

You only need one or maybe two people to deploy the solution. You need a technician mostly for security.

What about the implementation team?

The vendor team were sales especialist, not consultants 

Which other solutions did I evaluate?

We evaluated in 2013 QLICKVIEW . 

What other advice do I have?

We're consultants. 

We're using the most recent version of the product. What we do is download the on-premises for testing in order to see the new capabilities.

It's a very mature tool with a lot of enhancements in the last two or three years. Our advice is that, if you are going to use it as an end-user, it's a very beautiful tool. If you are going to use it in an institutional way, you have to take good care of your ETLs and you have to design a very good data warehouse. That's what they don't do. That's what many, many, many organizations don't do. I don't know if that's the case with Snowflake or Microsoft Power BI.

You must take care of your warehouse information if you are going to have a very good design, granularity, and time framing after three months to one year of information.

The dashboards and the ETLs must do more work than Tableau. If not, you're going to crash. One of the problems that we had was due to the fact that Tableau said that you could reach the SAP information and that was not true. You need a third-party developer. That's an additional cost and additional training. However, with a solution like QlikView, they have a very beautiful integration with SAP.

I'd rate the solution at an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: We are a solution consultant and regarding BI we mainly work with Tableau
PeerSpot user
PeerSpot user
Director , Business Intelligence at a healthcare company with 5,001-10,000 employees
Real User
Top 10
Good community support, easy to manage, and useful for getting things done quickly
Pros and Cons
  • "Self-service is most valuable. Users can pick up quickly and do the resolution. There are a lot of out-of-the-box features, and it satisfies most of the needs. If users are properly trained, they can deal with any situation."
  • "We need big servers to perform the operations that we are doing. They should probably relook at its architecture."

What is our primary use case?

We have a lot of use cases. We use it for real-time finance dashboard, real-time operations dashboard, and marketing insights.

What is most valuable?

Self-service is most valuable. Users can pick up quickly and do the resolution. There are a lot of out-of-the-box features, and it satisfies most of the needs. If users are properly trained, they can deal with any situation.

The Tableau community is really good. If we have an issue, it is already answered in the community.

What needs improvement?

We need big servers to perform the operations that we are doing. They should probably relook at its architecture. 

There are limitations to the data source that we are building. We can put only 32 tables in a data source, which means we have to transfer some of the workload to a database.

For how long have I used the solution?

I have been using this solution for eight years.

What do I think about the scalability of the solution?

Scalability depends on us. It depends on how we are configuring it based on the users' needs and experience. It has nothing to do with Tableau.

We have about 70 active users at any time of the day. Even Tableau was surprised to see that level of active users.

How are customer service and support?

They're good. We have got enterprise support or premium support, so they respond quickly.

How was the initial setup?

It is easy to set up. It is also easy to manage. Ours is a huge implementation, and we have five people for maintaining this solution. They take care of user provisioning, dashboard creation, and other admin work.

What's my experience with pricing, setup cost, and licensing?

It is more expensive than other solutions.

What other advice do I have?

I would recommend it depending on the use case. If you have money to spend and want something done quickly, then definitely go for Tableau.

I would rate it a nine out of 10.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1258353 - PeerSpot reviewer
Lead of Business Intelligence at a energy/utilities company with 10,001+ employees
Real User
Good visualizations, and it is easy to create dashboards, charts, and graphs
Pros and Cons
  • "It is very easy to create dashboards, charts, and graphs."
  • "The Hyper Extract functionality is not as strong as that provided by Microsoft SQL."

What is our primary use case?

We primarily use Tableau for reporting and visualization. Visualizations are important to us.

My role is primarily concerned with financial planning and financial reporting. 

What is most valuable?

It is very easy to create dashboards, charts, and graphs.

What needs improvement?

The Hyper Extract functionality is not as strong as that provided by Microsoft SQL.

Tableau is not as strong as Oracle OBIEE in some regards.

For how long have I used the solution?

We have been using Tableau for six years, since 2014.

What do I think about the stability of the solution?

Tableau is quite stable.

What do I think about the scalability of the solution?

The scalability of Tableau is very good and I don't have an issue with it.

How are customer service and technical support?

I have not dealt with technical support personally. We have a specific person that communicates with them.

Which solution did I use previously and why did I switch?

We also use Microsoft BI and Oracle OBIEE for reporting. I think that Tableau's features are much better than those of OBIEE and although Microsoft BI has better performance, Tableau is still the one that I like the best.

Tableau is much more expensive than Microsoft BI.

How was the initial setup?

The initial setup is not complex. This is one that I can set up on my own, unlike a solution such as EnterprsieOne, which I cannot.

What's my experience with pricing, setup cost, and licensing?

The professional version of Tableau is quite expensive. This is in comparison to some other products, such as Microsoft BI, which is only $110 per year.

What other advice do I have?

I would rate this solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user251337 - PeerSpot reviewer
DHS HQ at a government with 10,001+ employees
Vendor
Good for quick visualization and being able to quickly consume unstructured data, but not so great when it comes to data exchange/integration and data mining
Pros and Cons
  • "It’s good for quick visualization and being able to quickly consume unstructured data to play around with."
  • "It is not so great when it comes to data exchange/integration, data mining, etc."

What is most valuable?

It’s good for quick visualization and being able to quickly consume unstructured data to play around with. This is good way to show a demonstration/prototypes of dashboards and scenarios for design discussions on reporting requirements or to show what the data is telling us when it comes to features of data integration, OLAP services, data mining and extract, transform, and load (ETL) capabilities.

How has it helped my organization?

Good for adhoc visualization of an unstructured dataset which comes from other sources outside of source systems that you can overlay on top of the structured data and you have to get a quick visualization dashboard prototype going. It helps with the Agile design build and can be used in our current operations analytics work to overlay multitude of data sources that we know of. Can always work offline, which is nice. It’s good for organizations with very limited staff to do quick report builds and dashboards that can be put on our SharePoint site for sharing or on reports when responding to data caps. I use it a lot for design discussions so I can communicate the gaps in data sources for data exchanges or to generate a storyboard prototype of how the data is to be used in visualization but where we need to have data exchange/ETLs on.

What needs improvement?

It is good for its use if ad hoc, offline, or needed for quick turnaround on reports/dashboards. It is not so great when it comes to data exchange/integration, data mining, etc. I rely on what’s available in current versions to see what APIs and plugins that I can use and they have Open Source on GitHub is a plus to share things to re-use.

Room for improvement is more on data integration features that are agnostic to any solution platform but can be plug and play to be able to reuse what was built out Tableau in any other platform of work.

For how long have I used the solution?

Over five years, and the past three more for integrating the use of a similar family of tools where Tableau is one of a few options in our environment, where these services are considered for quick-hit items as needed, given time, dollars, and analyst skills.

What do I think about the stability of the solution?

No.

What do I think about the scalability of the solution?

Yes, see other answers. Scalability per user defined elements are okay but not so much for enterprise wide reuse. Per license cost can have some work done to it to make it more affordable on the recurring maintenance end of things. I would like to see more subscription based models.

How are customer service and technical support?

I don’t have to use it much since I can get much of this through current site materials and social media blogs/videos.

Which solution did I use previously and why did I switch?

I didn’t switch. It was just a matter of seeing where Tableau makes sense as a service to use in our environment, which is for the simpler, not so complex, but quick turnaround. Worked with other technology stacks that are similar, like Information Builders, SAP, Microsoft, Oracle, SAS, MicroStrategy, IBM, Salesforce, Qlik, etc. I find Tableau the easiest on visualization and its license model straightforward. But when it comes to scaling to other interoperation work, not so great on the wizard template, to do data mining/exchange. It doesn’t have that robust analytics and intelligence self-learning feature that comes with other tools.

How was the initial setup?

It’s straightforward, like any typical software. You have just got to understand what the various versions of API and plugins and what they can do. Though I have noticed that there were situations where it was said it was able to do things, but not until a later version. It needs better communication on that front.

What's my experience with pricing, setup cost, and licensing?

License small scale and run with it to get a business case going on its use. Give the licenses only to those analysts you want to do quick turnaround visualizations and those that know the data sources/data (those that don’t will just have access to tool and that compounds a problem with giving you something nice to look at but no meaning behind it, which I wouldn’t recommend). Look to existing platforms of one’s current BI environment and see if you can have a server license which can reduce the per user licenses.

I wish there was more of a subscription model with the pricing when it comes to Tableau, so you can get all the latest version upgrades/features if you pay monthly/annually, rather than buy straight up licenses that you lock to a baseline version and have to pay for upgrades later on. It limits how many users you can get on the thing, and it's not like you will use it all the time.

Which other solutions did I evaluate?

Yes, we did an alternatives analysis of all the product line options against our criteria of need in our environment, where recurring cost, time to implement, and other interoperation, security, platform scalability, architecture, etc. factors play a role. The majority were mentioned above.

What other advice do I have?

We always have the latest versions of Tableau (part of the package deal), so we can have the latest in APIs and integration hooks and plugins needed across our platforms of OBIEE, SQL, etc.

Tableau is good for quick visualization once you have the data, but not such a great interoperable tool or getting to multiple sources without a lot of work and know-how. Good for pulling in unstructured data and doing quick reports/prototypes. Does require some stronger business analytical skills rather than your novice user (and technical with regards to use of API and plugins).

If new to the analytics/BI market, use it, as it's good for getting you jumpstarted to understanding your data/data sources and to envision what you can use the data for. It's a good starting tool for that. If more advanced or need it for interoperation, I suggest looking to see how it fits with your current environment and determine where best to use it as it shouldn’t be your only option as the features are not robust enough to scale for everything.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros sharing their opinions.