Tableau Reviews

It was used for a project in the capital finance domain. We used it to develop the dashboards. My role was to plan the development activity and prepare the dashboards.

All features are valuable. It is very user-friendly, and it is mostly drag-and-drop. If we have the dataset available, then we can develop any dashboard very quickly.

SAP BusinessObjects has some semantic layer designs that give the flexibility to do ad hoc reporting or dashboard designing. If that can be brought into Tableau, it would be great. We have the data in the database, but we should also be able to bring something between the database and the dashboard and do some semantic layer modeling for ad hoc reporting requirements.

I have been working with this solution for almost three years.

It is very stable and user-friendly. It is overall good.

I have used it only for building dashboards. I have not used it much for other areas, so I don't have any inputs about its scalability.

Its users are from the finance department. There are more than 20 people for that project, and they are using different dashboards. Its usage would expand in the future. They have a plan to also use it for machine learning. I am not sure if that would be a different team or if we will be involved, but machine learning is coming into the picture in the future.

We have experienced people in the company. Whenever we are stuck with something, or we want to achieve something new in Tableau, we consult each other. We help each other, and we get the solution. There is also a Tableau community where we can get help.

For any technical support, Tableau administrators raise the ticket and get the answers from Tableau's support team.

Initially, they were working on SAP BusinessObjects, and then they moved to Spotfire. After that, they moved to Tableau. SAP BusinessObjects was more for reporting purposes, whereas Tableau is for dashboarding purposes.

We also liked Tableau, and that's why we moved to Tableau. It is more user-friendly, and it is also better than SAP BusinessObjects in terms of look and feel. 

Its initial setup was easy. The time taken to develop dashboards depends on the dataset that we want and the data source with which we have to connect. We have to create the data source and the dataset, and then we have to develop the dashboards. If we have the datasets available and we have an understanding of the requirement, then in one or two days, we can develop a dashboard.

For its maintenance, there are three people in a project, and we are able to manage their requirements. There is one administrator and two developers.

If you have more ad hoc requirements, then I would recommend evaluating other BI tools as well. If you have fixed requirements and you know what type of dashboard or reporting is needed in advance, and it is not going to change very frequently, you can go for Tableau. It is very user-friendly. If product owners or users want to go for a self-serving tool, Tableau is the best option.

I am satisfied with it, but there is always a scope for improvement. This is a competitive market, so there will always be some scope for improvement. I would rate it a nine out of 10.

We use it for internal monitoring purposes.

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. 

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.

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.

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

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.

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

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

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

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.

I'm a customer and an end-user.

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

I'm collecting some information and some reports from SAP and sending them to users as a graphical report. That's basically how I use the product.

The new pre-built application of Tableau is amazing.

The initial setup is simple.

It's a very stable, reliable solution.

You can scale the solution.

The dashboard has a lot of great options. 

I'd like it to work without the workflow or pushing options from the build, every time you need to do a refresh. We need a workflow for pushing the data to the cloud or to the server when you are using the pre-built application, the new application.

In the cloud sometimes the performance is a little bit slow.

I've been using the solution for two and a half years.

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

I have found the solution to be scalable.

At my organization, we have about ten to 15 regular users. 

We use it pretty extensively - at least once a week.

I'm not sure if we actually have plans to increase usage at this time. 

So far, I haven't needed any help from them. It's a good application in and of itself. I haven't needed technical support.

I used a little bit of Power BI. I know Tableau better, so I moved to Tableau Arabic.

The initial implementation process was straightforward. We did it without any problems.

Since the solution is on the cloud, you don't need a lot of staff for maintenance tasks.

You do not need an integrator or consultant to assist you in the implementation process. We were able to do it ourselves. 

We have a standard license that we renew yearly.

I'm an end-user.

I'm using the latest version of the solution.

I'd recommend Tableau to others. It offers good performance and the dashboard options are solid. 

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

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. 

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. 

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

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. 

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.

Tableau support could be improved.

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.

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.

We had professional services to help us.

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.

I rate Tableau eight out of 10. 

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

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

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. 

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. 

We've used the solution since 2013.

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 

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

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.

Positive

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

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.

The vendor team were sales especialist, not consultants 

We evaluated in 2013 QLICKVIEW . 

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.

When we work with CXOs to create dashboards we use Tableau. C-level employees like a CXO, a CEO, a VP, prefer to work with Tableau. It's easier and better for them.

For Tableau, the most valuable feature is the user experience and the quality of the end product.

One thing I would want to change for Tableau is to have a lower-cost model. It's pretty high for enterprise deployment.

In the next release, I would like to have the capability to call machine learning models within Python while I'm building a dashboard. The value calculation should be a machine learning model, which is running somewhere else, on say, Amazon. These tools give good outputs, like calculated fields and all. But today the outputs are not straightforward. In simple terms, I need machine learning on the fly. That is not there.

I have been using the solution for four or five years.

I would say the solution is very stable. We have not had any issues in using the product at all.

The solution does have scalability issues. When the data size increases, the product slows down and doesn't work right. In addition, it's very expensive to scale.

The only other solution we use and have explored is Power BI from Microsoft.

The solution deployment was pretty simple and straightforward.

We deployed the solution with our in-house team.

It's an enterprise solution, and we have all licenses. Tableau has multiple licenses; there is a reader, a developer, and an administrator.

If there are 50 or 100 users wanting to use Tableau, it's pretty expensive. The license is very expensive. We have 20 to 30 users in our company.

Because the solution is a drag and drop tool and what unique features we need or what we want to build, we cannot build using the tool. So we use JavaScript for that. We write our own code and build our own solutions.

My advice would be that all solutions are good, but it depends on your use case. If you are building something for C-level employees, use Tableau or another solution.

I would rate this solution an eight out of ten.

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

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.

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.

I have been using this solution for eight years.

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.

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

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.

It is more expensive than other solutions.

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.

You can create many different types of visualizations and charts, ranging from simple to highly advanced. And if you're doing advanced analytics, you can leverage Tableau by integrating it with other solutions. You can also do a lot of automation in Tableau, and collaboration is quite good too. 

They currently don't have a great Workday connector. Right now, Tableau can connect to more than 80 different types of databases or data sources, but it's challenging to connect with a few types, like Workday. So if they can come up with a better version or a connector for Workday, it will solve a lot of problems.

I've been using Tableau for around five years.

I can say Tableau is highly scalable. Now that they've introduced Hyper, you can create an extract of more than 5 million rows in minutes and then do your analysis. So that's a very optimized way to analyze a lot of data. That's why many other companies like Amazon use Tableau to create their visualization, reports, and charts, considering that their data volume is very high. 

Tableau technical support is quite good. The Tableau community is also helpful. 

Tableau's pricing structure is unusual. So let's consider all the other competitors in the market. For example, we have products like Tableau, Power BI, Cognos, and QlikView in the data visualization segment. Compared to those, Tableau is quite costly. Their desktop version is expensive, and if you're using their servers, it's even pricier. Of course, they give discounts to bigger organizations. For example, we are premium customers to them, so we are getting it at a different cost, but for an individual, it's costly.

I rate Tableau nine out of 10. I would recommend this to anyone who is coming into the data analytics space.