Inline tds odbc driver

Privacy policy. Starting with version Version If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please select Read in English at the top of this page.

You can download different languages from the US-English version site by selecting available languages. For details about this release on Windows, see the Windows release notes. If you need to download the packages for offline installation, all versions are available via the below links. Tableau Capability Customizations Reference. Any existing workbook or data source file that already has an enabled customization section will use only the customizations that it supplies, not the TDC file.

Important: Tableau does not test or support TDC files. These files should be used as a tool to explore or occasionally address issues with your data connection. Creating and maintaining TDC files requires careful manual editing, and there is no support for sharing these files. When you create a TDC file, you need to save it to the right location so that it can be used by your connection.

If you create a workbook that you want to publish to Tableau Server, then you need to savethe TDC file to the server as well. The next section is crucial because it identifies the vendor name and driver name of the database provider for this TDC file's data source. Each TDC file can bind to only one data source type.

Name the file odbc-sqlite. Note: The file must be saved with a. Go to and open the Tableau Desktop log file, and look for a record similar to the example below to verify that this customization file was applied to your new connection.

The TDC file must be saved on all server nodes for consistent behavior. Go to and open the Tableau Server log file, and look for a record similar to the example below to verify that this customization file was applied to your new connection. Let's assume that you've made an ODBC connection to your data source and verified that you can get the metadata and data you need. Now you need to determine if creating an extract or if using the live connection as is gives you the functionality you need.

If it does, the TDC file you created is sufficient, and there is no need to customize your connection. If the TDC file is not performing the way you want it to, you can customize the connection. Review the lists to see the customizations you can use to tune your ODBC connection.

The following customizations can help improve functionality for data sources with default capabilities that are not optimal. You will need to consider which other capabilities should be explicitly enabled, since Tableau will not be able to determine those automatically.

Tableau works best with at least entry-level conformance, so this value should be at least 1 if the data source supports it. A value of '' indicates support for all standard SQL aggregate functions. Some data sources are so severely limited that Tableau is unable to complete the steps of creating a connection.

Occasionally this is due to crashes within the driver, which cause Tableau to cease working. You can use a global TDC file to prevent Tableau from issuing queries or checking for capabilities that might be associated with the instability. Create a TDC file with the listed vendor name and driver name. See Vendor and driver name for an example.

If you have libodbc. Create a data source configuration — odbcinst -j can be used to display where unixODBC looks for configuration files. Now, assuming everything is configured correctly, you should be able to connect to the database from Iguana.

If you try simply working with the database, you may find that it fails with a mysterious error message. Archive: Iguana 5 Documentation Switch to Iguana 6.