Tableau offers a first-class connector to Vertica that you should be using instead of the "Other data sources (ODBC)" connector. Please try using that connector instead and report back if you continue having problems.
I hope this helps,
Apologies for resurrecting an old thread - but did the original author of this issue ever get a satisfactory resolution?
We are having the same issue and are getting nowhere fast with Tableau support!
Solution Services Architect
T: +44 1179 435 818
I second Rich's inquiry and comments. Given the date of the original post, it appears that this bug has been existent for two years, at minimum; yet, it's not listed among Tableau's "Known Bugs" page. Are there any Tableau support reps on here that could at least provide us more detail on the generic error message? That may help point us in the right direction so we can work on our own solution.
Unlike the original poster, our ODBC connection is not based on a Vertica database. Our options are confined to using the ODBC connector. Any assistance would be appreciated.
... Ours also!
We have developed an ODBC driver which works in desktop with a direct connection to the database (via proprietry driver), but doesn't work when used as a shared / server published connection.
We are also experiencing the same issue using the Microsoft ODBC driver for SQL Server included with Windows - ("Other data sources (ODBC) -> SQL Server").
Deepraj - if you are using the Microsoft ODBC driver for SQL Server, have you tried to use Tableaus native SQL Server connection? We have found this works fine... there seems to me that there is some issue that Tableau haven't yet addressed with regard to distributing an ODBC connection.
Rich, yes and I agree; Microsoft connections are fine, but ODBC connections seem to require a slightly more complex configuration. Just a couple of tips below:
- In addition to the end-user workstation, confirm that the applicable ODBC driver has also installed on Tableau Server
- The ODBC DSN names for both the server and client computers has to match
- Since Tableau Server does not support Kerberos at this time, the server-side DSN will need to authenticate with the underlying data source using embedded credentials of an AD-based service account. Ensure that this service account has access to the underlying data source.
Hope these help
Currently the design of published data sources using ODBC connections doesn't allow for aggregations.
While support for this is a current feature request, I would suggest creating an Idea in the Ideas forum asking for support for aggregations when using published data sources and ODBC connections.
When available, native connections do support this.
I realize this is an old thread, however publishing a ODBC data source will now support the use of aggregates in Tableau Server 9.2
Please see the 9.2 release notes for details and upgrade online help doc for upgrading information.
"In Tableau Server, when using a published Other Databases (ODBC) data source, you couldn't add an aggregated measure to a view."