What's Changed - Things to Know Before You Upgrade
Version 10.5 includes some changes you should know about before upgrading.
For information about what's new in Tableau Server 10.5, see What's New in Tableau Server.
The following sections summarize the significant changes to Tableau Server 10.5 and provide links for additional information.
Hyper powers the new Data Engine in Tableau Server 10.5 and introduces the changes described below. For more information, see The New Data Engine in Tableau Server.
Beginning with version 10.5, Tableau Installer automatically installs Data Engine when you install file store, Vizportal, VizQLServer, data server, or backgrounder and cannot be installed separately. Every node that has an instance of one of these processes will also have a single instance of the data engine process. You can no longer configure more than one instance of data engine on a node. To learn more about Tableau Server Processes see Tableau Server Processes.
Previously, in versions 10.4 and earlier, for distributed installations, the backgrounder process launched temporary instances of data engine (tdeserver64.exe) process during extract creation or refreshes. In Tableau Server 10.5, a single instance of data engine is installed automatically when you install backgrounder. The backgrounder process uses this single instance of data engine that is installed on the same node. For more information on configuration recommendations, see Distributed Installation Recommendations.
Upgrade may affect your current configuration for a multi-node cluster, especially if you have certain processes isolated on a separate node. For more information, see Upgrading to Tableau Server 10.5.
Beginning with version 10.5, new extracts use the new .hyper format. The improved data engine can read both the .tde and .hyper file formats, so the latest version of Tableau Server can continue to view and read workbooks that are using .tde extracts.
Existing extracts will not automatically be upgraded to the new .hyper format during the Tableau Server or Tableau Desktop upgrade process. Only when certain extract tasks are performed on the .tde extract, the extract is upgraded to the .hyper format. For example, an automatic or scheduled refresh will upgrade a .tde extract to a .hyper extract.
- For more information on extract upgrades, see Extract Upgrade to .hyper Format.
- For recommendation on how to handle automated or schedule refresh tasks before you upgrade, see Pre-Upgrade Tasks.
NOTE: Use the Extract API 2.0 to create (.hyper) extracts, which requires Tableau 10.5 and later. If you are using Tableau 10.4 and earlier, continue to use the Tableau SDK to create .tde extracts. The Tableau SDK is no longer being maintained. For more information, see Extract API 2.0.
Upgraded extracts are not backward compatible. After extracts are upgraded from .tde to .hyper format, they cannot be opened or refreshed in Tableau Desktop 10.4 and earlier. Tableau recommends that Tableau Server and all Tableau Desktops in your organization be on the same version and be upgraded to 10.5 on the same schedule. For more information on specific extract compatibility scenarios, see Impact of extract upgrade
The site roles Viewer (can publish) and Unlicensed (can publish) have been deprecated and are no longer available. Users who have either of these site roles on Tableau Server 10.4 or earlier will be reassigned in Tableau Server 10.5.
|Deprecated site role||In 10.5 is reassigned to|
|Viewer (can publish)||Viewer|
|Unlicensed (can publish)||Unlicensed|
You can now create project hierarchies when you want to segment content into sub-sections within a larger area. For example, you might create a project for each department. In each of those top-level projects, you can separate content based on how the audience uses it, such as connecting to certified data versus in-progress collaboration. For more information, see the following articles:
Using tabcmd, you can specify only a top-level project in a project hierarchy. To automate tasks you want to perform on a sub-project or content in a sub-project, you must use the equivalent Tableau REST API call.
Not all actions are available through the REST API. If you use Server on Windows and want to run an unscheduled extract refresh or append a file to an extract, a possible alternative is to use the Tableau Data Extract Command Line Utility.
Version 10.4 includes the following change you should know about before upgrading.
For information about what's new in Tableau Server 10.4, see What's New in Tableau Server.
The following sections summarize the significant changes to Tableau Server 10.4 and provide links for additional information.
The Precise dashboard spacing feature added to authoring can cause elements in existing dashboards to shift by a few pixels. This can impact layouts of dashboards that have been designed with precise layouts or floating elements. We suggest you confirm layouts of existing dashboards during upgrade testing. For more information on the Precise dashboard spacing feature, see Precise dashboard spacing in the What's New in Tableau help for authors.
There are no changes in version 10.3 that impact upgrading.
For information about what's new in Tableau Server 10.3, see What's New in Tableau Server.
There are no changes in version 10.2 that impact upgrading.
For information about what's new in Tableau Server 10.2, see What's New in Tableau Server.
Version 10.1 includes some changes you should know about before upgrading.
For information about what's new in Tableau Server 10.1, see What's New in Tableau Server.
The following sections summarize the significant changes to Tableau Server 10.1 and provide links for additional information.
The Setup program for the tabcmd utility is no longer installed to the
\extras folder when you install Tableau Server. The utility itself (tabcmd.exe) is still installed to the primary node when you install Tableau Server, but the separate Setup program for installing the utility on other computers is not. If you need to install the tabcmd utility on additional computers, you can download it from Tableau Software. For details, see tabcmd.
Version 10.0 includes some changes you should know about before upgrading.
For information about what's new in Tableau Server 10.0, see What's New in Tableau Server.
The following sections summarize the significant changes to Tableau Server 10.0 and provide links for additional information.
The changes described in this section have a significant impact on the upgrade process.
Manual uninstall of previous version is no longer required
Starting with version 10.0, you can upgrade Tableau Server without first manually uninstalling your previous version (when the previous version is 64-bit 8.2 or later). When you run the setup program, the existing version of Tableau Server is recognized and is uninstalled during the upgrade process.
Note: If you are upgrading to version 10.0 and want, you can manually uninstall the existing version before you upgrade, following the same upgrade process as you would in versions earlier than 10.0.
Setup gives you a backup option
If you follow the new workflow and let the Setup program uninstall your existing version of Tableau Server, you are prompted during the setup process create a full backup of your Tableau installation. This backup is a safety measure and is created for use in the event of an unexpected issue during upgrade. If you already have a backup of the current state of your installation, you can skip the backup during the upgrade to save time. For more information, see Tableau Server Upgrade Backup Options.
If you configure a two-node installation of Tableau Server, you are limited to a single repository. If you are upgrading from a two-node installation that has two repositories, you will be prompted to remove one instance. For more information, see Install Tableau Server on a Two-Node Cluster.
As of version 10.0, the licensing server is located at tableau.com. In versions earlier than 10.0, this was located at tableausoftware.com. Any firewall rules or proxy configurations that specify tableausoftware.com must be updated for version 10.0. For more information on proxy settings, see Configuring Proxies for Tableau Server.
Note: Earlier versions of Tableau Server will continue to access the licensing server on the tableausoftware.com domain. If your organization is running versions of Tableau Server prior to 10.0, continue to use tableausoftware.com for proxy and firewall settings.
With version 10.0, Tableau Server can be installed on a 2-core computer. (Previously, Tableau Server required at least 4 cores.) The 2-core configuration allows you to test Tableau Server on constrained hardware and is intended only for trials and prototyping. For more information, see Minimum Hardware Requirements and Recommendations for Tableau Server.
With version 10.0, Tableau Server is available only as a 64-bit application. For information about upgrading a 32-bit version of Tableau Server to version 10, see Upgrade from 32-bit to 64-bit Tableau Server.
With version 10.0, Tableau Server no longer supports Microsoft Windows Vista or Windows Server 2008 (Windows Server 2008 R2 is still supported).
With version 10.0, Tableau Server no longer supports Microsoft Internet Explorer 8, 9, or 10.
This change impacts customers doing an initial install of Tableau Server on Windows 8.0 or Windows Server 2012 (non-R2). Neither of these operating systems supports Internet Explorer 11.
To complete configuration of Tableau Server you must use a browser on the server computer to add an administrator account. This requires browser that is supported by Tableau Server. This means that on Windows 8.0 and Windows Server 2012 non-R2, you must use the latest version of Chrome, Firefox or Safari. You can uninstall this browser after the initial installation is complete.
Note: This only affects an initial installation and configuration, because no browser is required when upgrading or restoring Tableau Server.
For more information on the Microsoft policy for supporting Internet Explorer, see Microsoft Support Lifecycle.
Version 10.0 of Tableau Server does not support legacy compatibility modes in Internet Explorer 11 and higher.
This change impacts you if your users view web pages that have Tableau views embedded in them and that set Internet Explorer to compatibility mode with HTML
DOCTYPE values. This can be an issue with SharePoint configurations that force compatibility mode. To avoid having users view web pages that put their browser into compatibility mode, either adjust configurations so that Internet Explorer is not put into compatibility mode, or use another supported browser, such as Chrome, Firefox, or Safari.
The API Server process (
wgserver) has been removed from Tableau Server. The process was available but disabled by default in version 9.3. The API Server process was formerly used to support the REST API, but as of version 9.3, this functionality was moved to the Application Server process. The API Server process is now removed, even if you explicitly enabled the process in a previous version of Tableau Server. For information about changes to the REST API, see What's New in the REST API.
Note: For historical reasons, some
tabadmin configuration options will continue to use "wgserver" in the option name, but this does not refer to the old API server.
Version 9.3 includes some changes you should know about before upgrading.
For information about what's new in Tableau Server 9.3, see What's New in Tableau Server.
The updates to Tableau Server 9.3 have the following impact:
New default configurations based on hardware
The Tableau Server installer detects your computer's hardware and creates an optimal default configuration for a single-server installation and for the primary server in a multi-server installation. The new default configuration determines the number of processes to run for each Tableau Server process type.
When you upgrade from a single-server or multi-server installation in which you previously accepted the default configuration, the upgrade process changes the configuration to the new hardware-based default configuration. However, if you upgrade a server where you configured a custom number of server processes, the upgrade preserves the custom configuration—both for single-server and multi-server upgrades.
If after you upgrade you want to revert to the previous default configuration, use the following table to determine the number of processes to set in the Tableau Server Configuration utility based on the number of CPU cores on the primary server:
Number of Processes
|VizQL Server||Data Server||Backgrounder|
|Before 9.3||In 9.3||Before 9.3||In 9.3||Before 9.3||In 9.3|
|16 Cores or more||2||4||1||2||1||2|
Note: If the computer where you installed Tableau Server has fewer than eight CPU cores, the default configuration has not changed from running one of each process.
For more information on the defaults for 9.3, see Primary Server Installation Defaults.
For more information on setting the number of processes for Tableau Server, see Reconfigure Processes.
High Availability Postgres Repository - faster failover
Improvements to the failover process now mean that processes do not need to be restarted after the passive repository is made active. This means that the downtime for a repository failover is significantly reduced.
Distributed installation - manual worker upgrades
Due to an update in third-party software, an upgrade to version 9.3 requires manual upgrade of worker nodes. A prompt during installation of 9.3 will let you know that worker nodes cannot be upgraded automatically. for more information on upgrading, see Perform the Upgrade.
API Server (wgserver) deprecated
The API Server process has been deprecated. In version 9.3, the process is still available in Tableau Server, but it is disabled by default for new installations. The API Server process was formerly used to support the REST API, but as of version 9.3, this functionality has been moved to the Application Server process. If you explicitly enabled the API Server process in a previous version of Tableau Server, the process will still be enabled in 9.3.
Version 9.2 includes some changes you should know about before upgrading.
For information about what's new in Tableau Server 9.2, see What's New in Tableau Server.
The updates to Tableau Server 9.2 have the following impact:
Assign Permissions to Contents setting
Because content permissions can be locked to the project, the Assign Permissions to Contents button has been removed and is no longer available for projects and workbooks. For more information, see Permissions in Project Hierarchies.
Schedules Run in Parallel by Default
When you create a schedule in Tableau Server, the schedule runs in parallel, that is, it runs on all available backgrounder processes at the same time. Schedules finish more quickly when they are run in parallel, but you have the option of running schedules serially as well. For example, you may want to run a very large schedule in serial to allow other schedules to run at the same time. For more information, see Extract Refresh Schedules.
Version 9.1 includes some changes you should know about before upgrading.
For information about what's new in Tableau Server 9.1, see What's New in Tableau Server.
The updates to Tableau Server 9.1 have the following impact:
SAML authentication - logout
Starting with version 9.1, Tableau Server supports SAML logout. SAML logout is enabled by default and you can disable or enable it using the
tabadmin set wgserver.saml.logout.enabled false/true command.
If your pre-9.1 Tableau Server is configured for SAML authentication, the logout functionality will not work until you reconfigure the metadata for SAML. You must re-export the SAML metadata file and re-import it into your IDP. For more information about configuring SAML metadata, see Configure Server-Wide SAML.
Hidden fields in published data sources - unavailable for workbooks
Starting with version 9.1, workbooks respect hidden fields in published data sources. Prior to 9.1, workbooks using hidden fields automatically exposed these fields.
If a workbook that was created prior to Tableau 9.1 used a published data source with hidden fields, the hidden fields were displayed in the workbook. Starting with Tableau 9.1, the behavior changes:
If you are creating a new workbook that uses a published data source with hidden fields, those fields remain hidden in the workbook and cannot be used in calculations, sets, groups, and other object creation.
If you are working with an existing workbook that uses a published data source with hidden fields, those hidden fields are displayed in red in the workbook to indicate that the fields, and therefore the views and calculations that use those fields, are invalid.
You can address this issue in one of two ways, depending on whether you want to show the fields or not:
Show (unhide) the relevant fields in the data source, and then republish it, or
Update the relevant workbooks to exclude the hidden fields.
For information on unhiding fields in the Data pane, see Hide or Unhide Fields in the Tableau Help.
Clickjack protection - enabled by default
Starting with version 9.1, clickjack protection is enabled by default on Tableau Server. The protection has been available for several releases, but had been off by default. For more information on clickjack protection and how it impacts embedded views, see Clickjack Protection.
Note: When clickjack protection is enabled, embedded views that use the embed URL copied from the browser address bar might not load. These view URLs usually contain the hash symbol (
#) after the server name (for example,
http://myserver/#/views/Sales/CommissionModel?:embed=y) are blocked when clickjack protection is enabled on Tableau Server.
Tableau Server 9.0 includes some changes you should know about before upgrading.
The updates to Tableau Server 9.0 have the following impact:
Default start page
Any user-defined default start page will be reset to the Tableau Server default start page. Users will need to reset their default start page after the upgrade.
Starting with version 9.0, custom logos have changed in the following ways:
- The background for large custom logos is different based on logo location. On the navigation bar the background is black and on the sign-in screen the background is white. For more information, see Change the Name or Logo.
- The small logo option has been deprecated. There are no locations in Tableau Server where the small logo is displayed, so the option does not do anything.
Beginning with version 9.0, Tableau Server will not install if your computer does not meet the minimum requirements. This is true for upgrades and new installations, and for all computers in a distributed installation. The hardware requirements are:
64-bit Tableau Server—At minimum you must have 4 cores, 8 GB of RAM, and 15 GB of free disk space to install the 64-bit version of Tableau Server.
32-bit Tableau Server—At minimum you must have 2 cores, 4 GB of RAM, and 15 GB of free disk space to install the 32-bit version of Tableau Server.
For more information, see Minimum Hardware Requirements and Recommendations for Tableau Server.
Note: If you are upgrading Tableau Server on a computer that does not meet the minimum hardware requirements, you will not be able to install Tableau Server 10.5 If you cannot upgrade 64-bit Tableau Server because of hardware requirements but your computer meets the minimum hardware requirements for 32-bit Tableau Server, you may be able to upgrade to 32-bit Tableau Server.
High availability and failover
As of version 9.0, Tableau Server no longer supports automatic failover with a two-node cluster. To get the benefit of automatic failover, you need to install Tableau Server on a minimum of three nodes. One of these can include a minimal install (the "base install" option).
The option to use an external confirmation host is no longer supported. Any installation that is configured with an external confirmation will be upgraded without that host.
When you upgrade a two-node installation that is configured for high availability (automatic failover), you are given the option to add a third node. You can do so as part of the upgrade process, or at a later time.
The Tableau Software user
Prior to Tableau Server 9.0, if you installed the sample data and users, a user named Tableau Software was created. The Tableau Software user was the owner of the sample data.
Starting with version 9.0, no Tableau Software user is created. If you install the sample data, ownership of that data is assigned to the initial user that is created (the administrator user).
Internal PostgreSQL database password regeneration
Installing Tableau Server or upgrading from a previous version regenerates the password that is used by internal Tableau Server processes for communicating with the PostgreSQL database. This password is only used by internal processes and is not accessible to server administrators or other users. For more information, see Regenerate a Password.
tabadmin restore - Doesn't automatically restart Tableau Server
Starting with version 9.0, a
tabadmin restore command will not automatically start Tableau Server. If you want the server to start after doing a restore, use the
--restart option. For more information, see restore.
"Remember me" option
With version 9.0 of Tableau Server, there is no Remember me option on the sign in page.
Session ID in URLs
With version 9.0 of Tableau Server, the session ID at the end of server URLs is now indicated by an "iid" parameter,
:iid=<n>. For example,
http://localhost/#/views/Sales2015/SalesMarginsByAreaCode?:iid=1. This parameter replaces the hash symbol "
#<n>" used for the session ID in 8.x versions of Tableau Server.
Changes in view URLs may impact embedded views, API calls, and trusted tickets
In Tableau Server 9.0, view URLs have changed. We recommend that you generate URLs by clicking the Share link in a view in Tableau Server 9.0, and then use the resulting URL in embedded views, API calls, or trusted tickets that you created in Tableau Server prior to version 9.0.
Note: If you use view URLs that were created by copying the URL in a browser's address bar rather than using the URL generated by clicking the Share link, the views may not work as expected after you upgrade to version 9.0. This issue can be resolved by replacing the view URL with the Share link URL.