Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build mobile apps for iOS, Android and Windows Phone
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Automate decision processes with a no-code business rules engine
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!
Sumit Sarkar is a Chief Data Evangelist at Progress, with over 10 years experience working in the data connectivity field. The world's leading consultant on open data standards connectivity with cloud data, Sumit's interests include performance tuning of the data access layer for which he has developed a patent pending technology for its analysis; business intelligence and data warehousing for SaaS platforms; and data connectivity for aPaaS environments, with a focus on standards such as ODBC, JDBC, ADO.NET and ODATA. He is an IBM Certified Consultant for IBM Cognos Business Intelligence and TDWI member. He has presented sessions on data connectivity at various conferences including Dreamforce, Oracle OpenWorld, Strata Hadoop, MongoDB World and SAP Analytics and Business Objects Conference, among many others.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, 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 or appropriate markings.