Tableau Enterprise Reviews

Tableau is easy to use.

Tableau has so many functions, so sometimes it's hard to find the right solution quickly. I have to search multiple menu bars to find the right command.

I started working with Tableau two years ago.

In some projects, Tableau isn't stable. Sometimes it calls automatically.

Tableau is scalable. Right now, 200 to 300 people at my company use it.

Their web-based tech support is okay.

Setting up Tableau is easy.

Tableau's price should be lower so more people can access this application.

I rate Tableau eight out of 10.

We use Tableau to provide analytics and dashboards. We also use it to automate manual work.

You can create attractive dashboards that inform users using Tableau.

They must have a write-back solution. You must have the ability to write back into the database, otherwise, it prevents full automation.

That's one reason why people still need their own Excel sheets and other tools where they can interact with data that's already in the database. You win completely the moment you load that in, in a central way. You could say that you are completely automated.

They need a write-back; that is what is missing. If they get the write back to the database, they will be fully automated, but for the time being, they are not.

I have been using Tableau for two and a half years.

We are using version 2021.3.

It's a fairly stable product.

Tableau is a scalable solution.

Tableau is used by approximately 90 people in our organization.

We do not intend to increase our usage. I've asked for reports on how many users we get on a daily basis, as well as how many people use it and then don't use it for weeks. How long do they stay if they come in, and what are they looking at?

We are attempting to purchase a tool that will provide us with that information. We know which dashboards are popular, which are not, and why the popular ones are popular while the unpopular ones are not. We need to get an add-on that will tell us exactly what makes the dashboard sticky and what keeps people coming back to use it.

We use technical support, but I don't interact with them directly. Our IT support team is the one who helps us. Our IT support team works with Tableau support to resolve issues, opening tickets and tracking them.

Prior to using Tableau, I used Power BI.

We don't do a lot of installation. Once you have a server license, you can literally create it in the server now that you have a server license. There are no issues with installation.

The installation does not require a lot of time.

We have one or two engineers who maintain this solution.

We have a server team to deploy this solution.

We are paying an annual licensing fee.

I believe it is a good tool, and I would recommend it to others.

I would rate Tableau an eight out of ten.

We are using Tableau to make a dashboard used by our internal users, and then it is being used for a KPI report. This part is also shared with our customers. The customers access the web, and they check some limited version of the KPI report.

We are using the Tableau server for clients and desktop. The solution is deployed on-prem. We are kind of a 3PL provider, and we are using Tableau to meet the requirements of our customers. We are implementers.

We introduced Tableau because it provides many features that can be customized by users. We provide training to make the dashboard look how our business side wants, and they are manipulating the dashboard for their needs.

On the technical side, we are IT support and sometimes we provide some education and information on how to use the solution.

I think it would be much better if Tableau provided some API-based integration. I did try to integrate the Tableau web page and web dashboard into our own application. Some parts were successful, but other parts have some open points. If Tableau provided this kind of package with some integration, it would be much, much better.

The most valuable feature is that we can integrate with our own database, and it will display the KPIs. This is highly required from the business side.

An improvement would be changing the design of the layout of the dashboard from the business side. Sometimes there are requests for the possibility to enhance the performance and the data depending on what they need more of. It depends on the situation.

I have been using Tableau for about four years.

It's already using 32 gigabytes of memory, but the performance is not so good. It's very heavy.

We have roughly 20 people using this solution. Most users have the role of logistics operator. Most users are doing their job regarding logistics, and they take more effort to make dashboards.

Currently, we have a strategy to open the reports to all customers, but I think we should develop more business-related skills, not only with the system or in some application terms. Our users do not have enough skills or insights for the dashboard.

We are doing our own technical support by searching the technical Wiki or things like that.

Initial setup is straightforward because it's a simple concept.

I'm not sure how long deployment takes because this is usually managed by our data engineer. There's no strategy regarding deployment itself. We just make some temporal or test dashboard and then communicate with our users. After confirming, we just announce it with email, and then they start to use it as an official version of the dashboard.

We didn't use an integrator, reseller, or consultant for the deployment. The number of staff required for deployment and maintenance just depends on the case. Sometimes it will be simple, so there are only two or three people to make suggestions. After they apply that, sometimes we officially open it.

Basically, we prefer a permanent license. A one-time charge is much better.

We didn't really evaluate other options. Every application provides some concept of a dashboard in using the data in that application. We have our own homemade dashboard and our business application, but users normally don't use it.

I think Tableau has many features for display, like graphs or pie charts. We can change dynamically, but our own dashboard doesn't provide that. It takes much more time if we change the layout there.

I would rate this solution 8 out of 10. Tableau has many features, and it's very nice, but it is very heavy. Tableau has to consume a lot of server resources.

It has many options and features but it's complicated. The users are having problems or difficulties to adapt or to learn the Tableau software because there are so many features. The many possibilities means that users should run a lot of it. It takes time to get used to Tableau. From my point of view, it's harder to learn.

For those who want to implement this product, I recommend that they research it themselves.

Tableau is good for routine dashboards, and it has integration with Slack, through which it can send you daily updates.

Areas for improvement would be visualization and augmented analytics. In the next release, I would like to see automated insights from the data added to the dashboard.

I've been using this solution for about six years.

Tableau can be a little slow when loading, and it can fail with higher gigs or terabytes of data.

From working with my data analyst, I get the impression that Tableau can't take the load when scaling.

We had embedded technical support from Tableau in our enterprise, who was awesome and kept Tableau updated at all times.

Tableau is pretty good, interface-wise - it's easy to understand and to download data. It also has the most functionalities and capabilities of any tool. However, it doesn't have anything that differentiates it from its competitors, unlike Adobe Analytics' strength in visualization and data capture. If someone is looking for routine dashboards and wants operational dashboards, Tableau is the best solution. However, if they want to drive strategic decisions, they may have to look into a different product. I would rate Tableau as seven 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. 

I work in the hospitality industry and I use Tableau Online and Tableau Bridge with our food ordering company. In our specific uses, I have found that Tableau is very good for extracting data, rather than for working live on the data.

Although the process of transferring data to Tableau isn't the best, once the data is already on Tableau, it works completely fine. I will typically make use of layer aggregation and other operations such as slicing and analyzing it by getting right inside the data in various ways.

Due to the demands of our industry, we always have things that we would like to see more in-depth over different dimensions, such as restaurants, branches, cities, and so on. With Tableau's help, our company can aggregate all the raw data and then analyze by rows, to see, for instance, which restaurant is doing the best by comparing them with one another. It also enables us to easily split areas into zones and use the data to test for not only which restaurants are doing the best, but also where (i.e. in which cities and branches). 

Although Tableau isn't the best for us when it comes to processing and working on live data, it is very good at extracting data for analysis. Once you have extracted the data, the aggregate layers you can create, along with slicing and other operations, are very handy. It allows us to really get inside the data, and it is, in my opinion, better than any other tool I have used with the same pricing model.

Of the best analysis features, multi-aggregation layers come out on top for me, because they let you extract raw details while making multiple aggregations on different time levels and different dimensions, and you still manage to get your work done quickly without having to load a lot of data grouped over different dimensions.

Tableau Bridge is also a very good tool, however I can tell that it does need a few fixes and some maintenance. That said, it's still good for its first few years since release.

Most of the problems in Tableau Online that I have noticed have to do with performance or weird, inexplicable bugs that I can't pin down. For example, you might try unloading some data, and you'll be waiting for a long time without anything happening.

These bugs always seem to happen when we perform big upgrades or do maintenance work, and we have had to send a lot of tickets for unexplained issues during these times. It doesn't seem to be a problem only for us, but also for customers all over the world, such as in Ireland, Western Europe, Eastern Europe, and the US, too.

As for future features, I would like to see major upgrades in Bridge and the Flow Tool, allowing us to do more data engineering work. I think it would give Tableau a big edge in the market to look into how to incorporate more data engineering tools into their product. 

Besides that, I would also like the charts to be more realistic and easier on the eyes.

I have been using Tableau Online for three years now.

The stability is okay. It's not 24/7, but you can say it's stable enough. In the start, it's more stable, especially compared to our OBIEE problems, which have taken two or three days to solve in the past.

It's easy to contact Tableau and ask to increase users or resources. They'll do it in the blink of an eye.

At present, we have 20 users, 12 of which are shift users. The majority of our users in total are board members or high-level managers. 

I wouldn't give their support more than a seven out of ten rating.

I have previously used Power BI, Qlik Sense, and Qlikview. I switched because Tableau was better in working with different sources compared to Power BI which was the only one that was truly on par. Qlik Sense and QlikView were easy to use but didn't have most of the features that Tableau and Power BI offered. Then there's OBIEE which I have used for the past two years, but it is quite difficult for non-technical users.

I also didn't like that Power BI is typically coupled with Microsoft Azure, whereas Tableau works well with AWS and Google which are a lot easier. 

The setup is straightforward. I mean, there's not much setup at all. It's easy for any mid-level user to do it. For example, I just used the documentation they provided and did everything myself. The documentation was sufficient
and the implementation strategy doesn't take more than 20 days.

I implemented Tableau by myself using the documentation they have made available. And for maintenance on one single node, you might need only two to three people involved.

For data extraction and analysis, Tableau is better than any other tool I have used with the same pricing model.

My ultimate advice is that you should know what the tool is capable of first and what your needs are. I think it's better to use the Server edition, and not Cloud, because there are a lot of problems in the Cloud version that don't seem to be present in the Server version. As for myself, I will likely switch to Tableau Server next year after doing a bit more research on how to do the changeover.

I would rate Tableau an eight out of ten.

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.

Right now I use Tableau for learning purposes, such as open data sources, trying to learn the various visualizations that can be done on it.

I liked the representation of the geospatial map. It was really cool to have that visual and be able to create hierarchies using the geolocation cities, states, just wording those names into appropriate provisions on the map. So that's really something nice. I feel the visualizations come out very pretty.

The price is definitely a point that can be improved because smaller firms, like my bank firm, don't use Tableau because it's an expensive tool. If there were an option that catered toward smaller firms, that would be great because Tableau does in fact help with a lot of different kinds of data sources. For instance, it lets you upload CSV on Excel. However, other tools that we currently use, such as Looker, do not let you upload Excel files for ad hoc analysis. So, definitely, this is something price-wise that can be catered toward smaller firms.

Creating variables, creating new fields in Tableau during analysis, actually adds columns to the data. That's something that could potentially give us an option. Do you want it as a column added to the data set or do you want it ad hoc in the visualization sheet? So if you create a measurement or a dimension, that creates a new column, but if you try to create a new filter directly on the visualization, it doesn't let you rename it. Basically what you see is just the calculation that you put in there. If you wanted to create something without making it an extra column in the data set, you can't just rename it to a more user-friendly short name. An improvement would be adding the ability to rename ad hoc creations if you do create a mark or a filter on the visualization. That doesn't really get added to the actual data fields.

I've been using Tableau for a few months now as a learning, research activity rather than a day-to-day activity at work. So I primarily was going to a Tableau Public Learning.

As of now, I haven't had any issues with the stability of the solution. Not any glitches.

Given that it's Tableau Public, I don't feel I could give the right answer to that. However, given that you could share your visualizations on a server without sending a file to people, scalability seems like a good option here.

I have not used their tech support, but I did refer to a textbook to learn how to use Tableau.

Tableau has resources for learning using videos as well.

My company currently uses Looker, not Tableau. I've been working on Tableau on my own time outside of work, trying to learn their free application, Tableau Public.

The setup was pretty straightforward. It doesn't take much to get it all set up.

Tableau is an expensive tool for smaller firms.

Do take time to learn the solution, because Tableau has a lot of features, a lot of complex visualization features that can make the visualization pretty powerful. I would advise people to learn it completely so they can use Tableau to its full extent rather than just ad hoc simple visualizations.

I would rate Tableau right at 8.5, leaning toward 9.