Tableau Enterprise Reviews

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.

We do tons of data analysis for the organization to try to plan for resources that are needed in the infrastructure, specifically servers, storage, and that kind of stuff.

There are about 30,000 devices that we have to manage. We need to make sure that we have what we need for our internal customers, which is a really tough task unless you can analyze data every single day. We look for all sorts of anomalies about how the devices are functioning or how they are growing in consumption. We pull up about 1.1 billion rows of information every single day about what they're doing, and then we've got to take that mountain of data and pick out what we are concerned about. Tableau is key in providing that information to our internal customers and just analyzing different sets of data, such as the asset data and the consumption data. It is just data analysis all day long. That's basically what we do.

The data visualization piece is most valuable. We do ad-hoc analysis or one-time shot things, but there are things that we have to track every single day. When our management and our customers want to see how things are changing, the dashboarding provides that information. Tableau is key in providing that data on a refresh basis. We use a data blending tool that pumps the data into Tableau, and we just schedule it to run every single day. So, the automation of the data and being able to present it to people who are interested are the most valuable features.

Its price is a concern. It is more expensive than Power BI. The other thing that I never liked about Tableau is its ability to handle large sets of data. To present the data in the dashboards, we have to stage it up exactly like it is going to come into the dashboard. We use another tool called Alteryx that does that for us. So, we manipulate the data, get it staged, and then push it into Tableau. Tableau is terrible at handling large data sets, and we knew right away that we couldn't use Tableau to do data manipulation.

I have been using this solution for ten years.

It is a stable and mature product.

It is able to scale to the user base that we have, but pulling large sets of data into the dashboard can be problematic. You have to reduce the data to only what you're going to present, and that's it. Otherwise, it is unusable in my opinion.

We've got hundreds of users on the product. When I came to this organization about five years ago, Tableau was fairly new, but it grew very quickly. Initially, only I and a couple of other people were using it, but now the user base has grown significantly.

Their support is good. They provide good training and all sorts of stuff.

We have a whole group that manages that. We don't get involved in it. We just ask for it to be installed and available, and they support it.

Its price is a concern. It is more expensive than Power BI. My guess would be that it is $1000 or less per year.

We might go for Power BI in the future because of its umbrella with Microsoft licensing. It is much cheaper for us to use Power BI, and some folks will go in that direction because they don't want to pay the higher license.

I would recommend getting Tableau to help with the training because there is a learning curve with it. Make sure the training piece is in place, and your account rep provides resources to get people started because it does take a little bit of training to get proficient at it.

I would rate Tableau an eight out of ten. It is not perfect, but it does the job for us.

In my consulting firm, I use Tableau for data visualization and data analysis. Alongside Tableau, I also use Python and, on occasion, SPSS.

The EU had recommended Tableau for use in some of the statistics offices in Africa, including government institutes in Ghana, and just last week I was using it to do a program for the Ministry of Monitoring and Evaluation. There, I used Tableau to convey selling points to buy Tableau, which is one example of the consulting work I do for clients. 

I also train others in visual analysis with the use of Tableau. This September, I trained 265 medical statisticians. Last week, I trained 13 staff from the Ministry of Monitoring and Evaluation. And soon, I'll be training another group of 20 people on Tableau.

Tableau is a good product for people like me who provide data analysis training because it makes my job far easier. It's a good product and very easy to use, making the introduction of key technologies extremely simple.

For instance, when you get data, and go in to analyze it, people ask, "This is numeric?" People start thinking about, "How do I get all these tools?" Tableau takes the data and automatically breaks it down into two dimensions and measures. That makes it easy for me when I'm doing training.

So what I would say to trainees is, "Don't worry about all these data types, when you are designing your questionnaire, because in Tableau it breaks them into two. And the measures are the ones that you are going to actually work on. You normally break them down by the dimensions." And that makes it simple for people to understand. Otherwise people don't know where to start when it comes to data analytics.

Tableau makes life very easy for not only myself but also for others, because you can quickly get into data analytics and visualization with it.

Tableau is easy to use. That's the first and most important thing. I not only provide consulting but I also train people to use it, so with its ease-of-use it's not as difficult for me to train executives and management staff, because they don't have the IT background, unlike when I'm using Python. They don't know anything about programming, so Python is more difficult.

Tableau is also, right from the outset, a self-service product. It's easy for anyone to understand and use. Some of the organizations that I introduce to Tableau are using the full-blown version, i.e. the commercial version, and they can very quickly start analyzing data with the use of the Ask Data feature, where you can simply drag and drop while querying for data with natural language processing. You type in English and it will pick the data and analyze it for you.

Those features are built into Tableau which makes getting started with data analysis very easy. And it's also got some pretty good built-in visualization tools. I would say Tableau is one of the best when it comes to self-service functionality.

I attended a Tableau conference recently, and a quick improvement came to mind. When I am training people how to use it, I've come across situations where I've found it difficult to explain relationships. For example, when you want to blend data or when you want to show relationships, like when linking multiple tables; well, if you're an IT guy, that's easy. But if you are not an IT guy, you don't know anything about entity relationships, and it becomes a bit difficult for others to follow along.

It takes me a long time to get people to understand, even up to the point where I feel that this is the lowest level that I can go in terms of explaining it. I realized that many people don't really have any experience or knowledge about relationships between objects, and it makes it hard for me to get my teaching across. 

So I was suspecting, and I think I made this recommendation, that Tableau could find an easier way to introduce relationships. For now, if you want to build relationships in Tableau, or even in Excel, you have things like Access modules and Sheets. But how do I know that I need to use one object with another for the relationship. And if you then put in a table, what do you do after that? You have to double click, but people don't know that you have to double click.

I was hoping that there's a way that they can make that process a bit easier, though I don't know how they will do it. Perhaps when you load Tableau and connect to a data source, there would be a prompt that asks you if you want to link two tables together. So if you want to link two tables together, maybe you do A, B, C, D.

That might help with the self-service idea. If you're talking about self-service, then it should be easy for people who do not have the time, or who do not have that IT background, to pick the data and use it correctly.

In addition, and more generally, what I would like to see more support for is predictive analytics. When you're doing descriptive analysis, Tableau is excellent, and it's easy to do. But when you are trying to predict something, like in Tableau's forecasting feature, it seems to require date fields, or it won't work.

But I can forecast something without relying on date fields; maybe I want to predict that a branch has to close if it doesn't want to make something soon. I don't need dates to do that. For this reason, I'm using Alteryx for predictive modeling instead of Tableau.

Overall, the only major frustration that I have had so far is with Tableau Public. I first used Tableau Public when I was building capacity, and when there was a later release to download and you wanted to upgrade, all your work would have to be manually re-entered. I don't know how they can solve that. I was expecting that they might make a release on this upgrade, and then I can hit upgrade and it will install over what ever I have already.

Otherwise, for now I think they are doing well and I know they're still adding a lot of features. But it does sometimes make our work difficult, for those of us who are building capacity, and who are regularly changing people around. It means you have to keep learning all the time.

Another small detail for improvement is that when you draw bar charts, the default color could be something more neutral like gray. Instead, the default is blue, and I don't exactly get why this is the case.

I've been using Tableau for the past three years now.

I contacted support when I had a problem with data entry in 2018 or 2019. I spoke to a man based in Ireland and he was super.

I had originally put the problem I had on the Tableau community support forum, but I didn't get the right answer. I've forgotten the exact problem but it involved connecting to a data set from an Excel file. Instead of the data field displaying the data for you, what I got instead was an error or no response.

It kept happening like that so I sent a message to support, who gave me some steps to follow. I followed them but it still did not work. However, I realized that any time I do it and it shows up and I click data,  it then suddenly goes off. I'm still wondering why that happened. I think it depends on the size of the file or some other reason. I have not tried it again because I'm a bit busy now but it's something that I want to go back to because support didn't give me a satisfactory answer.

They told me, "Do this." I said, "I tried it. It did not work." They asked me again to do something and I tried it, and it still did not work. But then I tried on my own, and this time when the problem came up I clicked the data interface twice to reload it. On the second time I clicked, it worked, but I don't think that is the right way to handle it. 

I used Power BI before discovering Tableau in 2016/2017.

At first I did not like Tableau, because Tableau initially put me off considering that I have a problem with how Françafrique countries, like in West Africa, are controlled by France to not buy anything from Anglophone countries. I've worked in 15 African countries. And for instance, in Ghana, we are bordered by Françafrique countries but they haven't bought things from here because France tells them, "Don't buy." Which to me is wrong. Why should you sit in Paris and dictate to Africans?

I also decided that, "Okay. I'm not going to go into any French country and work." So, for my consultancy, apart from mainly Côte d'Ivoire, I also said, "Look. It is the attitude towards Anglophone and West African countries, I'm not going to help anybody." Because my contract with the World Bank was to build capacity. So I decided I'm not going to go there.

So, when I saw Tableau first, the word itself made me think that this might be the same kind of product, and I would not even look at it, because I was against it.

I kept on using my Power BI until a colleague, another consultant who we met from South
Africa, said to me while I was demonstrating Power BI, "I think you can use Tableau." I said, "What is Tableau? I don't want it." He said, "Oh I don't know much about Tableau, but somebody told me it's easier to use than Power BI." He said, "Why don't you look at that?"

We were working on the same project and I told him, "No, I'm not interested, I will not
look at it. It's a strange product, I don't want to look at a different product." And the guy insisted, "Oh please, you must take a look at it." Because we were looking at the project like we're a team, I said, "Okay, I'll look at it."

So that evening I downloaded it and I realized that all the things that I'm doing in Power
BI, that requires some level of IT background, well, I don't need that in Tableau. So then I decided, okay, let me really look at it. Who is behind Tableau? I asked where is the name Tableau from? Where did you get that name from? Okay.

So that was the time I changed my mind towards Tableau, and to be honest with you I've not regretted anything for doing it. I'm quite happy about it.

Setup is not that difficult for me. However, I remember in Gambia, there was some initial difficulty when I was teaching how to set up the organigram for the National Social Staff System.

In the National Social Staff System, you have about 11 ministries involved and the coordinator, and it's the coordinating agencies in Bureau of Statistics. So I needed to set up the system so that all the other ministries can enter their data. And when you enter the data, the other ministry, let's say, Ministry A can also enter data. And Ministry B cannot see what Ministry A is doing.

Now, when I was doing it, it was not difficult at all, but because I had to handle other systems and leave, I tried to explain it to them but they found it a bit hard to grasp.

So where you have multiple alliances and you set them up like organizations, it can get a bit complex. Because there's differences within the same organization under different departments. It's not a big problem when you buy Tableau for one single organization, but when you set things up for multiple organizations like the National Social Staff System, it can get problematic.

The national system is made up of different entities: Ministry of Health, Ministry of Agriculture, Ministry of Finance, etc. They are different ministries and they don't necessarily need access to all of each other's data. But if you buy Tableau for each of them then that is fine but if it comes to a situation where they all come under one number and you're setting up, you don't want one ministry to see what the other is entering.

So there was definitely a bit of a problem there. But I can't blame Tableau because no matter what it is, sometimes you need a certain level of IT skills to get certain things done. 

At $70 per month, I think the price is a bit scary. I have a small consulting firm in Ghana, working in about 15 different African countries, and when it comes to our part of the world, $70 a month is a lot of money for software.

In fact, where Tableau was approved for use in Gambia, I had the EU pay for three years. But I know it's expiring soon, and I don't think they will have the money to renew. I don't know how they're going to do it. When you come to Africa, especially when you're on the net, we don't use it so much, so I don't know if there is something that they can do about pricing for people in the African continent.

Yet recently, I trained 265 medical statisticians on how to visualize their data, using Tableau Public. They were so happy. And they thought, "Oh, this is very easy for us to do." But when they asked me about the price and I told them, they said, "$70? But we can't pay."

So that for me is a problem here. And, mostly, it's a problem for everybody. There are some companies that can easily afford it, but the majority of companies cannot.

I have occasionally used IBM SPSS for similar work that I perform in Tableau, but I only use it when the client absolutely requires it.

I wouldn't tell people to go with Tableau just because it's the tool that I use. I would instead emphasize its remarkable ease-of-use and the way Tableau really listens to their users and comes up with frequent upgrades. 

I would rate Tableau a nine out of ten. 

We have been using Tableau for all sorts of analytical tasks. When I was having an ERP SAP practice, we used SAP analytical tools and IBM Cognos plus Tableau for dynamic display session purposes. Tableau ended up being the best solution. That is why we moved over to Tableau. We predominantly implement and use Tableau. 

It's a pure data platform. Everyone relies on Tableau. Our departmental meetings and reports for monthly meetings and reviews happen live on Tableau. We can prepare all of our KPIs on it. In fact, all of our KPIs can be placed onto one single screen and divided into nine tiles that can be further divided.

We can easily review and define all of our KPIs. The data is perfectly validated. It allows us to run corporate and board presentations purely on Tableau's visualization center.

It's an extremely good product with respect to performance and analytics. 

All the transactions that are happening are happening in SAP and some of the solutions are in Oracle as well. The combination, the data extraction which is filtered into authenticated, validated financial data, sales data, material data, etc, into Tableau platform is very useful for us.   

The solution makes for very productive and really informative decision making. It can lead the whole business and build a strategy across whole working departments.

The licensing costs of Tableau are on the higher side and probably if you wanted more adaptability in usage across business divisions you need to have more reasonable pricing of licenses of Tableau. Tableau is a standalone product. That is a disadvantage.

Due to the fact that it is a standalone product, it has to extract the data from other ERP systems or other bespoke systems and other data systems, etc. If you have big data systems and you have got other informed decision-making tools and the data is being extracted into Tableau it is dependent on many other platforms.

In contrast, if you use SAP vertical data systems and you have SAP's Data Hub, etc., then everything is vertically integrated. The whole data pipeline is vertically integrated and there is a visualization screen right there as well. Therefore, you don't normally have to go for a separate integration process altogether or need a data extraction solution.

In the end, Tableau has got two or three disadvantages in the sense that it is not a seamlessly integrated platform, end-to-end platform. It's purely a standalone reporting tool. On top of that, the licensing cost is extremely on the higher side. Thirdly, IT divisions probably are a little bit hesitant to use Tableau due to the fact that separate training is required, and separate skill sets are needed to develop everything. 

The cost of owning the solutions from Tableau is much higher compared to any other analytical solutions.

We've used Tableau for the past two and a half years or so.

Technical support is okay. It depends on the countries. I was in Australia for some time and there the support is much better than in India. This is probably due to the fact that a number of users are struggling with it and you get delayed support here. It's better to use Tableau proactively and develop a center of excellence in our organization. That is what I did and it helped us out a lot. I don't have any complaints about technical support per se.

Tableau is undisputedly the number one analytical product in the world. I have given a long presentation to management and the CEO about what differentiates Tableau over other products such as Cognos and Hyperion, SAP, etc. Lumira also is a strong contender, however, Tableau is way ahead because of the dynamic reporting that is possible and the whole virtualization that is very easy to produce, or reproduce. The business users themselves enjoy working on Tableau much better than other solutions like SAP, Cognos, Hyperion, etc.

The pricing of the solution is a bit high.

We're only customers. We don't have a business relationship with the company.

We have not moved to the cloud so far with this product. Only SAP Ariba is on the cloud. The rest of our solutions, all analytical solutions, are on-premise solutions only.

Businesses should know what exactly they can do with Tableau. It's not just a visualization center or dashboard. You can contact a lot of assets that are in use - such as institutional analytics, predictive analytics, and prescriptive analytics. It can integrate with any artificial intelligence learning solutions and analytic solutions. That is where big data analytics play an important role. Modern business is more focused on all sorts of big database analytical solutions, especially for retail and other larger CRM business.

A company needs to decide answers to questions such as "how do you extract data?" or "Which department wants what data?". They would definitely need to have an initial, extremely focused approach of implementing it, with the full participation of the business teams. That is how a successful Tableau implementation needs to happen. However, it doesn't end there. You also need to educate business users or corporates on the solution as well.

Tableau is an extremely good product. I'd advise other users to use all aspects of and take advantage of its capabilities. Tableau has many licensing products available and a whole analytical model should be under one platform rather than going for bits and pieces from Oracle, IBM, SAP, Microsoft, etc.  Tableau is undisputedly the leader of the whole analytical solution and it should remain so only because it should have a larger use phase.

The training of Tableau is good, however, users should be aware that the consultants' availability across various countries is limited. I'm from Bangalore and if I need a Tableau consultant it's very difficult to locate one. You can, however, often find freelancing consultants. They can also get the job done.

Overall, I'd rate the solution seven out of ten.

There are so many solutions on the market. Primavera solution is a project management software. There is no product that can beat Primavera in the project management functions so you have many such project management products, SAP Project Manager, Product and Portfolio management is there, Microsoft Project is there. There are other Oracle project management solutions out there and then Primavera is there. 

When Oracle purchased this solution, the popularity of Primavera died out. I've personally stopped recommending that particular product. There are others that cost less, so why use that one?

Tableau should learn from Primavera, and ensure it builds its user base and market its abilities so that corporates understand the depth and breadth of its usage. Many only use 10-20% of its capabilities. It's the duty of Tableau to ensure potential use cases are advertised and more information is disseminated to corporates to help them understand how it can benefit them and why that should adopt it.

Our clients from different industries use Tableau for data visualization purposes. 

Tableau's most valuable feature is its ability to connect with various data sources and display real-time data on three different dashboards. It stands out in handling and utilizing data compared to other products like Oracle BI.

There should be stronger data modules for the platform.

We have been using Tableau for the past one and a half years.

The platform is relatively stable. I rate its stability a nine out of ten.

The platform is highly scalable. I have five clients, and the total number of users across all clients is around 300 to 400. I rate its scalability an eight out of ten.

The platform's technical support services require improvement. There should be enough support during the deployment.

Neutral

The platform is deployed on the cloud and on-premises. Its initial setup is straightforward. It took about an hour or two to deploy. I rate the setup process as a nine out of ten.

The pricing of Tableau should be better to remain competitive in the market, especially when compared to alternatives like Power BI. By adjusting the pricing, it can appeal to a broader range of markets and attract more customers.

I rate the platform an eight out of ten.

I have used Tableau in the past with other clients for enterprise-level data visualization for financial and manufacturing industries. I have also used it for documents dashboard and different kinds of KPI visualizations. I'm currently using it for academic purposes. In my current organization, we are not using Tableau. We are using Power BI.

Tableau is very flexible and easy to learn. It has drag-and-drop function analytics, and its design is very good. It is a very good tool, and it basically brings life into data with good design. We have been creating a lot of interactive visualizations and dashboards.

It has a public version. There are public communities from where you can get a lot of examples for practice.

Its price should be improved. Its price is much higher than Power BI and QlikView.

Programming is not easy on Tableau. For programming, you have to have a separate model. They should include programming directly on the web portion of the Tableau desktop so that people can write Python or JavaScript code for customizations instead of using a different model. Currently, Tableau Data Prep is a separate application that you have to purchase. It would be helpful if they can include Tableau Data Prep and programming languages such as R, Python in the next version.

Tableau Public, which is a community version, doesn't allow you to save your work on your desktop. They should allow it. Currently, you can only upload it in the community.

I've been using Tableau for almost eight or nine years.

It is very stable. 

It is scalable. They have a cloud version, and you can implement it on the cloud.

Their technical support is good. Our own IT can also manage it, and I can also get support from Tableau.

We also use Dimension, Power BI, and QlikView. Domo is also there, but Domo is a little bit more expensive. Microstrategy is also a little bit more expensive, and it has different media storage.

Its installation is straightforward. It is a one-click installation. 

I installed it myself on my laptop.

Its price is higher than Power BI and QlikView. Tableau costs around $70 per user per month, whereas Power BI is around $8 to $9. QlikView is around $30. 

Tableau has various prices for various models such as Creator, Designer. 

I would recommend this solution if you do not have budget constraints. It is a very good solution with excellent visualizations. I plan to keep using it for academic purposes.

I would rate Tableau a nine out of ten.

I am using it for my personal use. I'm using Tableau Public. It is a downloadable version. I downloaded it to my system and installed it.

The feature that is currently most valuable is the import feature where I can link to an Excel data source. I'm not using it with any other data source, such as SQL Server. I directly link it to an Excel sheet, and if I change anything in that Excel sheet, the changed data immediately gets reflected in the virtualization. This is something that is very convenient for me as of now.

Its documentation can be improved so that a user can get a good hands-on experience. Tableau is well documented, and on their website, there are a lot of tutorials that are available for free. I started my learning process through those tutorials, but there are certain loopholes in those tutorials, which only got filled through a couple of good YouTube channels that talk about Tableau. YouTube helped me a lot. So, the documentation could be better, I understand that it is evolving day by day, and with more usage, there would be more such documentation.

There are a couple of features that are only available in the cloud version, and I would like to see them in the hosted version. We can only use them in a demo or temporary account for 10 or 15 days, but I would love to see those features in the hosted version that I am using, which is Tableau Public.

I have been using Tableau for almost one and a half years. 

It is stable, but at times, I have seen that it doesn't work for certain datasets. If the data is not correctly sanitized, there are chances that you would end up having no visualization at all, even after spending a lot of time. So, sanitization is a must in Tableau as of now. Other than that, I've not seen anything else. There are no bugs, but if the data is not sanitized, you will not get any visualization. That is a problem. 

It is pretty scalable. There is no doubt about it. In the cloud version, a live data source can also be integrated. So, it seems pretty scalable, but I've not tested how scalable that version is.

I don't have any experience with their technical support. Whatever I've learned to date is from online resources such as YouTube and my personal sources. I've not contacted Tableau support.

Its initial setup is quite straightforward. It took me a while to understand that this version is also available for free for users like me who want to understand the data visualization part, but its installation is pretty easy.

I'm using Tableau Public, which is free.

I compared it with QlikView, which is a leading data visualization tool, but because I had heard a lot about Tableau and I had seen that there is a lot of scope in the market to get hired, I decided to go ahead with Tableau. 

I would rate it an eight out of ten.

I have used Tableau to generate visualizations to calculate system trend analysis for business. 

Tableau has been very helpful to give a high level of insight into our business.

Tableau's most valuable features are user-friendliness and have a connection between multiple source systems. You can publish a report by using Tableau Public and there you can make your data online, not only batches of data, you can use it as an online analytical tool.

There are more than a powerful tool in the market, such as Microsoft BI.

I have used Tableau within the last 12 months.

Tableau is a stable solution.

I have found Tableau to be scalable.

I would recommend this solution for large enterprises.

I have not contacted technical support. However, after reading many reviews others have found the support to be good.

The setup and deployment of Tableau are very easy. I did not have a problem.

The price of Tableau could improve. The license is too expensive. 

There is a 14-day trial version available to those who want to try it.

I would recommend Tableau, but if any organization wants to use it, they can see if the solution fits their business requirement. There is a very competitors market and with a low price. Those wanting to use this solution need to study the requirements to know which repository to use.

I rate Tableau a nine out of ten.