1 of 1 people found this helpful
This KB article has the answer http://kb.tableau.com/articles/knowledgebase/desktop-and-server-compatibility.
Here's what I found with my own testing:
Desktop v8.2.7 desktop
Published v8.2.7 workbook to v9.0.5 server w/o issues. When I download the published workbook from TS, I was able to open it with Desktop v8.2.7 (the version it was created) and later version v9.0.1.
From v8.0 to v9.0 may be too big of a jump though...I worry that you may run into weird issues. Best practice is to have Desktop and TS on the same version. Go through the KB article above and look for your specific use case. I also suggest you test it out in a non-prod environment.
Thanks John for your reply.
Also I am facing Tableau Error while trying to use the workbook created in TD8.0 and open in TD 9.0. I see the below error. TD8.0 and 9.0 are installed on same machine.
"ERROR 2624: Column "<column_name>" does not exist The table "<table_name>" does not exist. Unable to connect to the server "<ip>". Check that the server is running and that you have access privileges to the requested database."
Currently for TD 9.0 I have HP Vertica DB(Vertica ODBC driver version 7.1) installed.Has this error something to do with version compatibility between Vertica database version and ODBC driver for TD 8.0?
Updating Vertica driver to v7.1 should've resolved the issue. Is the old version of driver still on the computer? What if you uninstall the old driver and try again? I suspect TD v9 may be trying to use the old driver,
Uninstalling the old driver (6.0.1) the workbook(created in TD8.0) doesn't open in TD 9.0, shows the following message.
The drivers necessary to connect to this database are not properly installed.
To connect to this database, perform the following steps:
Click the following link to go to download drivers: 'Download Drivers'
Follow the instructions
Attempt to connect to the database again.
Detailed Error Message:
Unable to connect to the server "<ip>". Check that the server is running and that you have access privileges to the requested database.
Upgrading to 9.1 Desktop version resolved the issue.