Sumit Sarkar demystifies some of the confusion around Tableau certification for third party ODBC drivers.
DataDirect has unrivaled experience building ODBC connectors for Tableau for impressive organizations like VoltDB, Hewlett Packard, NetSuite, ServiceNow and COINS with the DataDirect OpenAccess SDK. But there’s a lot of fear, uncertainty and doubt out there about third-party ODBC drivers for Tableau, and I frequently have ISVs approaching me with the question, “How do I know this will work?”
As a trusted Tableau technology partner, we want to set the record straight. Configuring third party ODBC drivers is fully documented by Tableau.
Many of the customizations are related to differences in SQL syntax generated by Tableau and capabilities across available ODBC drivers and data sources. Tableau has two types of customizations that can be configured in a Tableau data source file: Tableau specific capabilities and ODBC API calls to SQLGetInfo. The naming of these customizations follows a convention of 'CAP_' for Tableau capabilities and 'SQL_' for the SQLGetInfo API calls.
In other cases, you’ll see customization name=’odbc-connect-string-extras’ which are simply passing driver connection properties to the ODBC connection string in lieu of configuration from the ODBC Administrator. For example, refer to Appendix D for SQLLite Customizations.
For a specific example, check out this article written by Prashant Khare from DataDirect R&D on how to customize and brand ODBC connectors built on DataDirect OpenAccess SDK for use with Tableau. He walks through the step by step process to customize the Tableau data connectivity experience.
The following example TDC file contains the customizations that are applicable to OpenAccess drivers. The connection customization section in the TDC file will have the Driver and DBMS/vendor names that the ODBC driver returns. Tableau uses this information to associate specific connection customizations with a single type of ODBC data source.
'DataDirect OpenAccess SDK 8.0'
In addition to data visualization, we also run millions of tests in our QA labs that include commercial off the shelf (COTS) applications across data integration, enterprise reporting, data preparation and data federation. So the question you should really be asking is, “how do I know whether my ODBC client will work across the full range of ODBC applications that are important to our customers?”
If you’re interested in building an ODBC driver to use with Tableau or another tool, go ahead and contact us, leave a comment below, or tweet me: @SAsInSumit. I’m looking forward to hearing from you!
Technology researcher, thought leader and speaker working to enable enterprises to rapidly adopt new technologies that are adaptive, connected and cognitive. Sumit has been working in the data access infrastructure field for over 10 years servicing web/mobile developers, data engineers and data scientists. His primary areas of focus include cross platform app development, serverless architectures, and hybrid enterprise data management that supports open standards such as ODBC, JDBC, ADO.NET, GraphQL, OData/REST. He has presented dozens of technology sessions at conferences such as Dreamforce, Oracle OpenWorld, Strata Hadoop World, API World, Microstrategy World, MongoDB World, etc.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.