KNOWLEDGE BASE

Datasource Not Reflecting a Structure Change on the Database After Being Replaced


Published: 25 Jul 2016
Last Modified Date: 06 Oct 2017

Issue

When trying to upload a new data source to Tableau Server to overwrite an old data source, and using this new data source to replace the old one in Tableau Desktop, workbooks behave as if they are still connected to the old published data source.

Additionally, the following behaviors can occur:  
  • The following error message might occur: "An error occurred while communicating with the data source: Invalid column name. Statement could not be prepared."
  • New column names are not reflected.
  • Workbook shows the new pill as red and an exclamation mark in front of the field in the dimensions pane; they these exclamation marks disappear after saving, closing and re-opening the affected workbook.

Environment

  • Tableau Server 9.3.0 - 9.3.6, 10.0.0, 10.1.0 - 10.1.9, 10.2.0 - 10.2.4, 10.3.0 - 10.3.2
  • Windows Server 2012
  • MySQL
  • Microsoft SQL Server
  • Oracle

Resolution

Option 1:

  1. For Tableau Server 9.3 or 10.0, upgrade to Tableau Server 9.3.7, 10.0.1, or a newer version. For more information, see Upgrade Tableau Server.
  2. After upgrading Tableau Server, open a command prompt as an administrator, navigate to the Tableau Server bin folder (located by default at C:\Program Files\Tableau\Tableau Server\<version>\bin)  and enter the following commands:
    tabadmin set DataServerRefreshMetadataPerSession true
    tabadmin config
    tabadmin restart

Option 2:

For Tableau Server 10.1, 10.2, or 10.3, upgrade to 10.1.10, 10.2.5, 10.3.3, or a newer version, see Upgrade Tableau Server

Cause

This behavior in 9.3 and 10.0 is related to a known issue (ID: 524007) which has been corrected in more recent versions.
Because the solution can have some performance trade-offs, the setting which corrects this issue (tabadmin set DataServerRefreshMetadataPerSession) is turned off by default.

In 10.1, 10.2, and 10.3, this behavior has been further corrected by changes made which resolve performance trade-offs (ID:625285), and use of 'DataServerRefreshMetadataPerSession' is no longer required.
 
Did this article resolve the issue?