Tableau Enterprise Reviews

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.

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.

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. 

We use Tableau to make dashboards and valuable information and insights available for management. We are creating some solutions and a dashboard, and people are using it to see the information. We use it globally across 118 countries.

It is basically the manufacturing clients we have all across the globe. They want to measure the production level, how we are getting the product delivered to the customer, and where they are lacking. They want answers to questions like "why are we not getting it up? Where do we need to improve?" They are preparing and analyzing which steps are taking too much time to get that delivered.

Tableau has helped improve our organization by enabling layman people to use it.

I like the calculation feature. I would not say it's such a good feature in Tableau, but if you have the knowledge, you can make that feature visible to everyone. It's not a feature that we can drag and drop and get the information. But whatever the data, whatever the calculation, I'm able to do. It's basically the knowledge base. Whatever knowledge I have, I can make that information public and publish it for management.

Many things have to be improved in Tableau. Right now, we make the calculation, and then we get that information. It would be better if business users could do that. I would ask the people at Tableau to provide that option to business users to get that information in one click.

It would be better if they automated some calculations. There should be more automation in Tableau. However, there are many things in automation mode, but it is very limited at the moment. We need automation for people who do not know much about Tableau. It would also be better if there were good community support like in Alteryx.

I have been using Tableau for the last three years.

Tableau has been stable for us.

Scalability depends on your data and how you make calculations. That becomes your scalability. About 20% of all our organizational users are currently using Tableau.

The technical support for Tableau is just online, and they don't have an option where I can call support.

We used OBIEE Oracle before, but it was very limited. We were moved on to a different solution because we saw it as a better option. Tableau is a better option when compared to OBIEE, and we have been using it for six or seven years. 

The initial setup is straightforward for people who are using it at a basic level. The advanced level is highly complex. The implementation strategy depends on the requirements we are getting from the people and the stakeholder. I would say that management is talking to us, and they are asking us to build the solution they want to have in place. They do not know whether it is technically feasible or not, but they know that this is the requirement. 

We implemented this solution on our own.

In Indian Rupees, Tableau costs about 30,000 to 40,000 per year. 

I would tell potential users that many things are not available in Tableau. Even Power BI is better than Tableau because there are many things that are good for the business. Effective visualization is not there in a Tableau. If I know of a better solution than Tableau, I would surely go for that other solution.

On a scale from one to ten, I would give Tableau a four.

I had a case in the dairy industry, and they had about 200 sales agents on the field. They needed some daily reports as well as some dashboards with the standard presentation of their goals and targets. So we prepared some dashboards and Kafka presentations of data collected daily and presented them to the field sales team. We drafted up some information for them about how to proceed with their daily targets. Tableau could visualize the salespeople's progress toward the targets. For example, it can use different colors to signify if the sales team is over or under its target. They can use this graphic to find what they need in their final reports. So if they are under a monthly benchmark, they can break down the graphic presentation, do final reports on a daily level, and find information on each day in the month.

Tableau's visualization features let you present information insights quickly and practically. So it's something which I prefer with Tableau. In terms of reporting, I have to point out the sheer quality and function of the Tableau server, but the first impression is that it's a great visualization tool.

If you mainly need a tool for BI reporting, it's not the best option. Tableau needs better abilities to generate simple reports, integrate, create databases, and work with data lakes. 

I can't recall ever having an issue with Tableau's stability. And also, I'm not sure how often our clients have had to update software or install patches, but I think it's pretty stable. I would consider it moderately to highly stable.

We've used local technical consultants and support in Serbia, so it was pretty good. I can't remember having any problem solving issues during the implementation. And later, during the exportation of this tool, support solved all our issues and incidents in a reasonable time.

Tableau also has a broad user community that's helpful and powerful. When you're using Tableau, you get a knowledge base with a lot of interesting and valuable information. So it's not hard to find some solution that's already prepared for simple presentations, like templates for visualizing reports in a novel way. 

I've used two editions of Tableau. The free edition was very easy to use and set up. The enterprise requires a desktop and the Tableau server, and it's not too complicated. However, it's necessary to have experience and some documentation. So setting up the enterprise version isn't easy for someone who has no experience, but it isn't too complicated overall, either. We had the support of a local company here in Serbia who rebuilt it. They are consultants who specialize in Tableau databases and everything necessary to implement this tool. So I can't remember any problems with the setup. It was relatively easy. They also had to set up the desktops, the Tableau server, and a couple of professional licenses to prepare basic reporting and visualization segments. Lastly, they just have to set up the end-user with everything they need to read the reports and see presentation and visualization.

Tableau's prices are relatively high for our market. I am from Serbia, so many companies in this market don't have the ability to pay for expensive software. My clients are quite satisfied with a lot of Tableau's qualities except for the prices.

I rate Tableau eight out of 10. I would recommend it for companies that have a specific need for a solution with strong visualization capabilities. 

I've used it for multiple purposes, for example, for exploratory analysis or just for dashboards for presentations.

I'd say it brings a centralized place to check day-to-day metrics and KPIs. It helps reduce the duplicated reports or sources of information to get the same data or information. Everyone knows that those dashboards are up to date. They know where to find the answers they're looking for.

I really like the interactivity of the dashboards.

I appreciate the fact that you can have filters and parameters so that users can really customize the view to what they want to see.

Truthfully, this solution offers pretty much everything that I need for my everyday tasks.

It seems that power BI is more targeted for report creation while Tableau is more of just a dashboard. If you need to have something report-like, or downloadable to share outside of the dashboard, that's where Tableau is lacking some features. 

Users would like to be able to export an Excel file when they see a table or something like that. That's not an out-of-the-box feature for Tableau.

I've used the solution for a year and a half so far. It hasn't been that long.

I've had a good experience with the stability. There are no bugs or glitches that I have experienced. It doesn't crash or freeze. It's reliable. 

We did have an issue with our server and it took a while for Tableau support to find a solution. However, that was a one-time thing. That's the only time where we've had issues with our server.

The scalability is pretty good. In our case, we did start small and we are now scaling in for our different departments. It's working great.

We are not a big group, however, I would say that we have around 80 to 100 users and that combines creators, explorers, and viewers - a little bit of everything.

We are getting used to it and using it more and more. We are expecting to increase usage in the future.

I've never been in touch with technical support. I cannot speak to how helpful or responsive they are. 

We did not previously use a different solution prior to adopting this product.

I wasn't around for the initial setup. I cannot speak to what the process was like and couldn't say if it is difficult or straightforward. 

We have some server admins that take care of it and work with Tableau to support it whenever needed. It's a group of people, however, I am unsure about the actual number of personnel that handles it directly. It might be three to five people. 

I've looked into Microsoft BI and downloaded some information about it recently.

I'm just an end-user of the product.

I'm likely using the latest version of the solution. 

Everything was implemented when I started, so I wouldn't know if there were any hiccups or best practices, or lessons learned from the process of setting it up. 

I'd rate the solution at a nine out of ten, from the experience I've had so far. It has helped us tremendously with our everyday reporting and things like that. I can do pretty much everything I want to do and it's been working fine for us.

We use Tableau for data analysis. We integrate 15 sources of data and then that data is brought into AWS. From the AWS, the data is uploaded onto a dedicated Tableau server where we have all our dashboards running. We then run code on the data to return results, such as the regression and causation.

The solution has great features which nobody can beat, you can do a lot of customizations, such as use different dimensions and colorize them. Additionally, you can use the numeric values for the customization, which is an exceptional feature.

There is a lack of visualization in Tableau which could be improved. For example, if you want to do a Sankey in Tableau, you have to do a lot of work to do it. Sankeys are available, they are for sale for a minimum of $400, which is out of the question. Whereas if I wanted to do a Sankey, it is simple for me to use a free visualization and put in the data, and from what I already have, receive a fancy Sankey.

Whenever it comes to specialized visualization, Tableau is an absolute failure.

The integration between Tableau and our statistics software or other software, such as Python is very loose and undefined. If they improve that it would be a benefit.

I have been using Tableau for approximately two years.

The solution is stable.

If I have web analytic data on session IDs, Tableau or Power BI both fail miserably in scalability because you are not able to go on a session-level and have 18 million rows fire up visually.

We have approximately 100 users using the solution.

The initial setup is simple.

We had a local team of two technicians that do the implementation and maintenance of the solution.

We are on an annual license which costs us $1,400 which is very expensive. Microsft BI is less expensive.

I have evaluated Microsoft BI.

The reason why we are not getting rid of Tableau is because of legacy reasons. Legacy, meaning it is being carried over and our organization does not have time and energy to transfer everything to Microsoft BI.

I will not give any credit to Tableau or Power BI for the very simple reason that everything is in the hands of the developer of how you visualize the data. There is not any magic in what Tableau is doing, the magic is from the developers who are creating the visualization. Any visualization tool which gives that capability sets you apart.

I would not use Tableau if I am working out of a financial organization because it is lacking fancy visualization. However, if I was a bank or a government organization where I am only looking at trend charts and bar charts I think Tableau comes out ahead of other solutions, such as Microsoft BI.

I rate Tableau a five out of ten.

We use the most recent version. 

We use the solution to engage the field teams and we integrate that with the data warehouse data and build the dashboards for them.

It is helpful that the solution provides access to one's own data. It allows a person to get insights out of the data provided by his tool, based upon the KPIs that the person wishes to look at. It all depends upon different use cases. We have dashboards for marketing people, field teams and executives. It all depends upon which insights a person wants, in which case he can prep the data accordingly. This is good. 

The most valuable features are the visualizations, the way they show the combination charts. This allows a person to jointly put in different measures in different axes and greatly facilitates the user in understanding the data better.

There should be a focus on memory data, which is the concept of Tableau. This is where they squeeze the data into their memory. Because of that, we see performance issues on the dashboards. The architecture should be improved in such a way that the data can be better handled, like we see in the market tools, such as Domo, in which everything is cloud-based. We did a POC in which we compared Tableau with Domo and performance-wise the latter is much better.  

As such, the architecture should be improved to better handle the data.

We are seeing a shift from Tableau to Power BI, towards which most users are gravitating. This owes itself to the ease of use and their mindset of making use of Excel. Power BI offers greater ease of use. 

For the most part, when comparing all the BI tools, one sees that they work in the same format. But, if a single one must be chosen, one sees that his data can be integrated at a better place. Take real time data, for example. I know that they have the live connection, but, still, they can improve that data modeling space better.

We have been working with Tableau for almost seven years.

The solution has pretty good stability. It's a robust tool, even though it has a steep learning curve. But, still, I feel that from the stability perspective, it's a leading BI tool in the market. It's pretty stable.

I personally don't like any BI tool to have that scalability. What we usually do is integrate scalability into our warehouse layer. We know how to scale up and down and we handle it there. We don't rely much on the BI tools to do that.

I am talking about the scalability of a program in general, be it in its relation with users or as it concerns dashboards. 

We recently started working with Tableau online and that particular solution is scalable. It ingests the hardware, the server capacity by itself. So, if users go from, let's say... 100 to 500, we don't see a dip in performance. It still behaves the same. Because of this new integration technology with the cloud, they are scalable in that regard.

We are in contact with technical support. One service we have is Tableau online. If we see a dip in performance, we raise a ticket to the Tableau support team, work with them and make certain they address our issues. I would rate my experience with them as three out of five. 

We used Tableau from the get go. 

While I was not directly involved in the setup, I know that it's not that easy. There is a need for a proper administrator who has experience in that field.

We used an integrator from Tableau when implementing.

Our experience was good and we were assisted with our implementation requirements. They were able to make notes to match our use case and answer all of our questions, including those concerning the number of users we have and how to set up the server.

I'm not part of the administrative group which handles the setup. I am mostly a consumer and responsible for building the desktop. I use the desktop version to build the dashboards and am not responsible for the server health check or maintenance. As such, I am not in a position to provide information about the staff required for maintenance, updates and checkups. There are a couple of people who are responsible for this, one from the customer side and another from our team. Both parties are in sync when undertaking these activities. 

I have no knowledge concerning the licensing costs of Tableau. 

The solution is mostly deployed on-premises, although we have also done cloud-based deployment. 

We have around 500-plus users making use of the solution and mostly 90 percent are viewers. We have very few creators or explorers. Creators comprise seven percent and explorers three percent. 

My advice to others would vary depending on their use cases, what they're looking for and the level of competency they have within their organization to use it. Tableau has a steep learning curve. So, it depends upon one's use case, the reason the person is going with that specific BI tool. The procurement department would need to evaluate the use cases very carefully, because there are so many BI tools available in the market. One's focus should be more on a centralized tool when bringing a new one to his organization. It should address all the answers to one's users, like what they're looking for. Definitely Tableau is good in the data discovery part and it can handle large data sets. So, all of these things should matter when one is trying to evaluate a tool.

I rate Tableau as a seven out of ten. This is because we are using it and it has a steep learning curve. It's not user-friendly. One must build a competency in creating the visualization and then support it. All of these things matter when one is evaluating a tool. That's why a shift is going towards Power BI.