Reviews (51-75 of 102)
- Easy connection to SQL Server. Easy creation of SQL statement, data source for reporting. Easy drag and drop report creation
- Flexible report formats
- Easy to set permissions on a per User basis
- We use Tab CMD extensively; documentation is poor (specifically on how to format some exports - a topic we recently had to rerseach).
- We leverage xtab reports a lot, and we run into the 16 column limit
We're a middle sized company, and only have 12 licenses because adding more is too expensive...
Tableau Server Review: "Decent product and good UX (except requirement for desktop client) but legacy underlying architecture"
Bad: Required lots of training to use all the features to create reports.
Bad: Interactive dashboards are hard to build and not flexible enough.
- Reporting through Tableau Server is just a matter of few clicks. Anyone with the correct user access can we the dashboards instantaneously.
- Using dynamic filtering, users can access the relevant sections of the reports without the need for any admin re-configuration.
- Thus far I have not seen Tableau generated reports being mobile responsive.
- Some of the navigation required to access workbooks, folders and projects can quickly get messy.
- Quick development time.
- Easy to administer.
- Lots of options for authentication.
- It's slow to start/stop the server components, which results in more downtime during upgrades.
- Hard to kill a data refresh manually.
- The ability to share metrics across an organization with one source of truth (published data source)
- Allows users the ability to author their own visualizations without having to purchase a Desktop license
- Subscription and Data-Driven alerting to alert users to changes in their data
- Add in the ability to search for fields while using web authorizing on Tableau Server. It's tedious to find the fields you want to add to a visualization when you have 100 fields and multiple joins to search through
- Allow web authors the ability to reorder the worksheets after creation
- Include ability to set up parameters while web authoring
- It always available and allows us to make it easy for users outside of the building get their BI info.
- It's easy to manage and takes very little daily or monthly maintenance.
- The subscription service really helps users stay on top of things with their alerts.
- Doesn't send out PDF versions of the dashboards.
- Tabcmd is old and needs to be updated to a visual client.
- It is sometimes slow opening dashboards and the new data methodology hasn't proven the improvement as promised.
- Is well suited at deploying BI dashboards to any audience that has a license.
- It not good at servicing users outside of the license for one-off reporting. Microsoft BI does this very well.
- Quickly get a feeling on how a line of business is performing by looking at a page.
- Out of the box easy to use, setup and produce visual data.
- Numerous ways to visually show the same data.
- Tabular reports could be expanded.
- Ability to quickly produce drill-down reports for quick numbers vs. visual displays.
- The ability for any staff to have access to only view reports at no additional cost.
- Ease of use
- Automatic data visualization
- Lower cost of ownership
- Interactive visual exploration
- Multiple data sources
- A license model need to be enhanced to capture small and medium business requirements
- Capability for data discovery
- Supporting the cloud functionality
- Since we're a healthcare organization, we're sensitive to security and privacy of information. Tableau provides delicate control of contents in terms of visibility in dashboards and has helped us effectively prevent potential information breach issues. It was easy to integrate Tableau Server with our active directory to control delicate privilege of data access depending on clinical specialty and roles.
- Since we have a variety of data sources from different systems--electronic health records, claims system, patient administrative system, radiology imaging system, etc.--harmonizing those sources and building and managing robust data connections in one environment is critical. Tableau is very good at that.
- Tableau provides great monitoring tools to manage bandwidth and performance, cleaning up unused data with extract and report.
- Tableau Server's computational efficiency of managing metadata is good, but it provides very minimum functions from the standpoint of server managers. As we add more data sources such as big data and external systems outside our organization, its importance becomes bigger.
- The new alert function on Tableau dashboard is promising, but it is only provided at a server level, not at a desktop level. In addition, it only provides minimum alerting reconfigurability. I understand it is a new function as proof of concept and look forward to seeing it advance.
- Tableau Server is good at monitoring usage of existing reports but provides little about monitoring data extracts and their data pipelining status.
- A new feature of integration with AWS is exciting but need to keep watching how it works well.
- It provided a way for us to host our visualizations and avoid distributing out the data.
- We could manage external users on this system.
- We were able to create one model but then limit which users could see various "views" of the data based upon what product was purchased.
- The licensing model was very expensive and required us to continually buy more seats all of the time. Long run, it's best for very small teams or when you get over the ~100 user mark, you can buy a server license which avoids the per-seat issue. Keep in mind that you still need to purchase the Tableau Desktop license for each of your data scientists/engineers who will be developing the visualizations ON TOP of these costs.
- We had to contract with a 3rd party to establish and manage an IIS server since that is the requirement for Tableau Server. It was unlike anything else that we were using.
- Tableau will tell you that the license grants you the ability to have three instances (dev, staging, prod), but in reality you likely won't use more than dev & prod, as the workflow was rather awkward for us.
- The ease of use - you don't have to spend countless of hours training users how to maneuver around the product. It is straightforward and self-explanatory.
- Ease of administering - I never took any formal training for this tool but have become rather good in creating groups with pertinent access and the role level security and administration is phenomenal. You can fashion your security just the way you want it.
- Updating and deploying the system is earth-shattering - it is very flexible and the cost is rather transparent.
- While it is easy to deploy and administer, it is also a very powerful monitoring and management tool as well.
- Alerting - is one area that tableau could improve on. I have submitted this as an enhancement feature, there is no way yet to state that when an account is reached a predetermined threshold, you can send an alert to a group to make decisions or act accordingly.
- Some other functionality that you have to use add-on tools to accomplish.
- Tableau's visual presentation of data is unsurpassed
- Tableau Server is easily integrated into various database and technologies such as Business Objects
- Because the Tableau user community is so large, we are able to obtain answers to the majority of our questions through news feeds and online user groups and communities.
- On the lowest level, many of Tableau's features and strengths are too complicated for the typical end-user
- IT expertise is required to fully implement Tableau Server
- Tableau Server is very weak in source-code versioning.
- I would not recommend Tableau out-of-the-box for use by an end-user
- Suited for better visualisations for reports and dashboards and for basic drill down.
- Not so great with slice and dice data.
- Easy for non-technical users to learn how to access and manipulate reports
- Workbook editing features provide a lot of customization potential without having to buy desktop -- as long as the defined data source does not change
- Wide variety of role and content-based permissions settings
- Great for distributed enterprise implementation and support -- lots of flexibility and use can be tailored lots of ways to meet the needs of different user groups
- Love that all the user and content data is easily available for analysis.
- More ways to organize content would improve. For instance, sub folders within the project folders would assist greatly.
- Tags used to label and organize should be able to be assigned and managed at the project level. Having just one set for a big, distributed implementation like ours makes them useless.
- Either updates need to be bundled more and released less frequently, or Tableau workbooks need to work in any version of Tableau Server and Desktop. A big challenge with our distributed approach is that some desktop users want to do every update, but IT can't be updating the server every month. It should not be a problem to have different versions on server and desktop, but neither product allows earlier versions to open files generated in new one
- Aesthetic value of reports generated is a plus.
- Intuitive system, not overly complex but not too simplistic either.
- Reliable platform, haven't had many notable issues of crashes, security penetration, or misinformation.
- Tutorials don't always help 100% - typically you have to go through their support team for special integrations. Once set up however, things run efficiently.
- You need to have reliably fast internet, otherwise it can get overloaded and you can possibly lose data.
- Easy to use
- Mobile device support
- Good investment return
- Lacks some functions in enterprise BI like robust scheduling reporting.
- Cannot build data source when you use a browser to create a new report.
- Monitoring capabilities are not comprehensive.
- Connects to disparate data easily
- Reduces the need for IT personnel to extract custom datasets
- Compresses and visualizes large amounts of data for quick display
- Helps keep dashboards organized
- Allows for flexibility by making published dashboards accessible anywhere
- Limited functionality of executing stored procedures and analytical cubes]
- Would like to see a stronger partnership with AWS and Azure
- For cases of "tell me something about X" for a data set I've never seen before such as data collected about blood transfusions, Tableau is fantastic at helping to make sense of the data and creating insights.
- In cases where the data is really messy, even though Tableau does not do full ETL it speeds up the analysis and distribution of analytics process by an order of magnitude or more over Excel, which is a huge win for us.
- Tableau's ability to aggregate at a variety of levels via table calculations is something that I haven't een done in other BI products (except via a ton of SQL), it makes a number of advanced computations easier for users to accomplish.
- Tableau's model for filtering and sorting is based on the individual worksheet. Though extensions have been made over time for filtering at the dashboard level, the level of functionality for filtering and sorting at the dashboard level isn't where I'd want it to be.
- Dashboard layout has definitely improved with version 8.0, and it's not quite the pixel perfect rendering that I want.
- Tableau Server can be up and running within 30-60 minutes on a clean install since their installation wizard is extremely easy to use.
- Tableau Server is easily administered by a small technical team of 1-3 people. The majority of administrative needs can be addressed through the web application directly. Others can be configured easily in configuration files or utilities.
- High level business users LOVE the rich, interactive visualizations that are possible using Tableau. No experience is needed to interact with and draw meaningful conclusions from your data using the web application.
- Analyst-level users can quickly learn to use Tableau Desktop in harmony with Tableau Server. With Tableau Desktop, users can create/modify reports and draw even deeper analysis.
- The Tableau Community and Forums are extremely active. However, Tableau Support is also proactive in terms of troubleshooting issues. They are responsive, follow up, and work on a first name basis.
- In Tableau Desktop / Tableau Server you can add micro-ETL processing, mapping, and other business rules directly in Tableau reports. This quickly becomes a danger to undermine existing back-end systems and their business logic. To avoid this, enforce concrete rules and structure for where business rules live.
- The Tableau ecosystem is fantastic and flexible, but there is a learning curve. Creating meaningful reports is difficult and it takes time to learn.
- Tableau Server introduced such a fast moving paradigm to reporting and visualization that it flipped our business users and technical team upside down. Suddenly we saw the millions of ways we could be slicing and dicing our data. Tableau Server opens up enormous windows for creativity and out of the box thinking. It's important to slow down and define a vision and long term goals for the reporting suite.
- Tableau does not offer any solution for version control on its workbooks / dashboards / reports.
- There is no clear way on how to QA/test Tableau reports given that it is primarily GUI-driven.
Tableau Server is a commitment. It is well suited for a diverse, large audience of consumers that are supported by a full-blown technical team of administrators and developers. The primary benefit of Tableau Server over Tableau Desktop is that your data published from Tableau Desktop is available dynamically through a web application to all users. If a small to mid-size company is interested, I would suggest simply getting a Tableau Desktop license as a low-risk entry point. Tableau Desktop is a single application that one technical person with direct access to the data warehouse can utilize to build reports on their own computer. These local dynamic reports can be emailed or turned into .pdfs.
In short, a key question to ask is: how large is the user base that will consume reports and how actively will they interact with the data? Tableau Server offers high levels interaction and may be overkill for a smaller company with more basic reporting needs. Tableau Desktop is a low-cost alternative for a single user to own and distribute visually rich yet non-interactive reports manually via email.
- Allows you to quickly visualize your data.
- Great for viewing data that has geospatial elements.
- Easy to share with others via publishing to Tableau Server.
- Not a one stop shop for summarizing large data sets (>1 million rows).
- Does not work well with Teradata (in my experience). There was a host of connectivity issues that were logged by Tableau support as bugs/defects that were going to be addressed.
- Performance is solely based on the amount of RAM your individual machine running the client app has (I would regularly see the Out of Memory error when trying to connect to Teradata).
- Requires customization in order to force a refresh of the the webpage when publishing the dashboard on Tableau Server (data refreshes in the background but webpage does not update at the same time).
During implementation, I was heavily involved with the Tableau consultants, stakeholders, and project managers to make sure that all requirements were met. I did testing myself and signed off on testing that others did. I provided my manager with constant feedback on our progress. We were able to get Tableau installed in one month based on a very aggressive deadline set by management. During this phase, I spent countless hours side by side with Tableau consultants to describe the performance issues we were facing at the time. Here are two of the main hurdles we faced during implementation: One of the main issues we faced was the use of Custom SQL to build our visualizations. Because the roles within my team were highly segmented, we preferred using Custom SQL vs. connecting live to the data. The reason for this is because I was tasked with building the visual. I was not tasked with building the query. The DBA I worked with would hand me the query and I would build the visual from there (creating the necessary calculated fields and formatting the data). Tableau advises its clients against the use of Custom SQL for performance reasons. In addition to performance, there are other drawbacks. We would notice that certain functions in the SQL statements themselves would not get translated correctly into Tableau’s Native SQL (there are workarounds for this). This issue was starkly apparent when connecting to Teradata. Towards the end of my role at SCE, I was working daily on improving the connection to Teradata. Before I left, I was able to take certain reports built in Business Objects and build them in Tableau (but this was only accomplished when connecting live to the data). Another issue was refreshing certain dashboards that were meant to run 24/7. Tableau has the capability to refresh the data behind the visual as frequently as every 5 minutes (I believe). But that refresh does not update the visual. In order for the refreshed query to update the visual, you are required to force the browser to update on an interval of your choosing. It is only with this combination that you can come close to seeing what is happening in real time. The workaround for this issue was to create an .html file that had the URL of the dashboard, which was published to Tableau server embedded in it. From here, you simply double click on the .html file and you would have your dashboard updating both the data (handled by Tableau Server) and the visual (handled by the browser).
Here is a list of the data sources that I would connect to when building visualizations:
1. MS SQL Server
3. MS Excel
5. MS Access
Data Blending – There were several instances where business requirements made it necessary to join data from two separate data sources (i.e. - MS SQL Server and Oracle or MS SQL Server and MS Excel). Tableau has an intuitive capability to recognize a data blend. This will be indicated by the use of the link icon next to the primary data source (it looks like an infinity sign). The ability to blend data together was very appealing in the conceptual sense. But there are limitations on the number of rows that you can blend together (I noticed a significant deterioration in performance after 100k rows). This seemed to always be our problem at the SmartConnect Operations Center. We would relentlessly push Tableau’s performance only to find out that our local machine didn’t have the RAM necessary to do what we wanted, or that Tableau was not intended for that specific application. Regardless, I learned a tremendous amount about how the application behaves in different scenarios.
Incremental Refresh – Sometimes it can be useful to use a Tableau generated extract. This is essentially a mini-Tableau database. My manager tasked me with building a report that would store historical data. The purpose of this report was to keep a running total of certain events in the network. The benefit of this report would be that it would automate a manual process that the end users were responsible for on a daily basis. Prior to the implementation of this new report, the end users were tracking the historical data using MS Excel. The challenge I faced was to find a way to store data from the daily query results. Because the original data source did not store historical data, it was necessary for me to take advantage of the “Incremental refresh” option available in Tableau. I do not advocate this method if the daily query results are on the scale of several hundred records or greater. This solution was feasible because the number of records were less than 100 per day. In addition, I worked with the end users and their team lead to create a backup method to get to the final row count in the instance that the Incremental Refresh option failed.
Experience with Teradata – SCE’s 5 million meter network produces around 15 million records per day in just one its tables. The data warehouse team built a set of views that could be accessed within the Teradata schema. After several attempts to connect to Teradata (unsuccessfully) using Custom SQL, I worked with both Tableau’s technical staff and SCE’s DW team to diagnose the problem. We spent multiple WebEx sessions documenting application behavior under various scenarios. Initially, my thoughts were that the problem was that the client application was trying to connect to a View versus a hard coded table. But Tableau assured me that the client application has no problem connecting to views. In this instance, the workaround was to connect live to the data. This worked on certain tables (with several joins in place) but not all. Finally, I was able to re-build a few reports taken from Business Objects. In order to do this, I extracted the SQL from the BO reports and then connected live to the same tables. The result was a visual that came very close to what was found in BO. The report reflected data that was aggregated in the form of a percentage. The percentage represented the performance of a particular district over a time interval (i.e. – 98.99% over a 3 day period).
Integration with ArcMap – The SmartConnect Operations Center’s business requirements made it necessary for me to find ways to enhance the mapping capability within Tableau. The default background map that is offered by Tableau falls short in the areas of zooming and satellite imagery rendering. Therefore, Tableau offers its users the ability to connect to a geospatial (WMS) server. To Tableau’s credit, the steps and information needed to connect to a WMS server are very simple. If you have the URL of the WMS, then you can connect to the server. In my experience, the biggest problem with using the layers from various WMS servers is in the rendering of the image. If your application requires a certain level of detail and/or the ability to zoom in to a certain extent, you may find that the static image stops rendering at a certain zoom level. In the SOC’s application, it was necessary to validate the latitude and longitude of meters in the field and their proximity to other meters (aka – the “mesh” network in wireless meter terminology) by visual inspection. When I left the SOC, I was in high-level discussions between Tableau’s technical team and SCE’s GIS team regarding the rendering of the different layers available through SCE’s internal WMS servers.
- You can "easily" add equations to the data that is displayed in your charts.
- We are able to provide "real time" reporting in Tableau. As the data in our service process occurs, it updates the report.
- We particularly like the mapping function. Again, we can easily provide data points in a map format in a multiple ways with dynamic icons.
- Great support.
- Drill down function: You can select a data field and drill down into the underlying data.
- Well, the viewer does not provide "drill down" capability. One of the nice features is the ability to drill down into the data that is displayed on the chart. It is easy to send someone the viewer to review a report, but it lacks this functionality.
- Tableau server is incredibly fast to deploy and easy to manage different permission levels for different roles and individuals
- Tableau server helps to share dashboards via cloud and it can be connected to live data sources so that the dashboard gets updated automatically when the data is refreshed. This was not possible with traditional dashboards.
- Tableau server enables integration of dashboards with existing enterprise applications so that data can be used by various departments to analyze business issues.
- Tableau server allows safe and secure connection to virtually any data source.
- The pricing plans should be made more affordable for small and medium businesses and continuous emphasis should be on reducing high maintenance costs which range from 20-25%.
- Tableau server is very user friendly and does not require much of technical expertise after the initial data preparation has been taken care of or if you are using basic data sources like a csv or an Excel file (which is highly unlikely to happen with an enterprise). So, there is still a need for someone with good technical skills to create the initial database and integrate it with Tableau server.
- It has a limited set of capabilities when it comes to advanced statistical or predictive features. So, Tableau server is best used to describe and analyse the past events but fails to predict the future events.
- Integration with other enterprise systems and applications is not possible and even customization is out of question.
- There is no provision for efficient reporting by scheduling reports and notifying the users once a new report has been generated. Also, data security is enabled by providing database access to the users which itself poses a threat to data security.
- Strength 1. Dashboards & visualization rendered in a browser looks almost the same as the original design in Tableau Desktop. As a developer, the last thing you want is to realize your published dashboard is a distorted reflection of your original design.
- Strength 2. Permission control. Although a bit more complex than other products (note I say "complex" and not "complicated"), Tableau Server provides great object and role-based permission control. Highly customizable.
- Strength 3. Workbooks decoupled from their sources for reuse (not mandatory but best practice). Although source/s can be monolithically embedded in a workbook for refreshing, they can be deployed as "stand-alone" sources (live or extracted) to be used and reused to feed into multiple workbooks.
- Strength 4. User-credentials management. Admins have the option to manage users and user groups via ad-hoc internal functionality or leveraging an existing Active Directory infrastructure. For large organizations, the latter allows adding a security layer by moving credential-granting responsibilities away from Tableau Admin's scope to an organization-wide security department.
- Data Governance. Adding functionality to make it easier to manage fields in a centralized manner, having a centralized data dictionary with synonyms, an impact analysis tool, etcetera, would be a big asset for large organizations (or smaller ones that do manual information lineage control).
- Simpler permission interface. Some improvements done recently, but still missing some functionality to see the big picture instead of having to review calculated user permissions at object level (project, workbook), same for data sources and a combination of the three.
- A graphic interface to see how extract schedules are designed to flow (using serial/parallel sequencing and priority values), as well as a report to show plan execution on a particular date or time-frame (highlighting where the extract failed).
First, the obvious: is Tableau Desktop the best tool for building organization dashboards? Does it cover all needs or falls short on some particular requirements that may become rather impractical when designed in Tableau?
Second: Out of the current (or expected) reports/dashboards, how many are (or will be) shared? Is it just a few, with the balance of them being in a tabular-format ? Do they require or would thy benefit from viewer comments or filtered shared views?
Third: Who will design visualizations and what's their complexity? Is it the IT department, a set of Power-users or a Reporting Expert? What's the weight of each of those roles in the overall dashboard inventory?
While the above only scratches the surface in the decision process, please think of it just as a bullet list on points you don't want to miss in your journey to a productive decision.
Tableau Server Scorecard Summary
Feature Scorecard Summary
About Tableau Server
Tableau Server is an enterprise analytics platform that aims to be easy to deploy and scale and help enable data-driven decision making throughout the user's organization.
Customers can deploy the way that makes the most sense for their organization - on-premises or in the cloud, on Windows or Linux, while integrating with their existing security and authentication protocols. Customers can provide governed data access while promoting sharing and collaboration with data, dashboards and insights. Customers can automate processes and workflows, manage content, define access for individual users and groups, and ensure accurate insights. Tableau Server gives customers visibility, security and controls that aim to help them empower their people with data.
Tableau's goal is to help people and organizations become more data-driven. With an integrated platform that strives to be easy to start and scale, Tableau aims to support the entire analytics journey, from data preparation, to deep analysis, to the shared insights that drive the business forward.
Tableau Server Screenshots
Tableau Server Integrations
Tableau Server Competitors
Tableau Server Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
Tableau Server Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Linux|
|Mobile Application:||Apple iOS, Android, Mobile Web|
|Supported Languages:||English, French, German, Spanish, Brazilian Portuguese, Japanese, Korean, Chinese|