![]() |
VOOZH | about |
The Tableau Bridge enables you to publish dashboards to Tableau Cloud while maintaining live connectivity with any data source. In this article, you will use the Tableau Bridge to maintain data freshness in a published workbook by listening for changes in the underlying SQL Analysis Services data.
The CData ODBC drivers offer unmatched performance for interacting with live SQL Analysis Services data in Tableau Cloud due to optimized data processing built into the driver. When you issue complex SQL queries from Tableau Cloud to SQL Analysis Services, the driver pushes supported SQL operations, like filters and aggregations, directly to SQL Analysis Services and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze SQL Analysis Services data using native Tableau data types.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
To connect, provide authentication and set the Url property to a valid SQL Server Analysis Services endpoint. You can connect to SQL Server Analysis Services instances hosted over HTTP with XMLA access. See the Microsoft documentation to configure HTTP access to SQL Server Analysis Services.
To secure connections and authenticate, set the corresponding connection properties, below. The data provider supports the major authentication schemes, including HTTP and Windows, as well as SSL/TLS.
Set AuthScheme to "Basic" or "Digest" and set User and Password. Specify other authentication values in CustomHeaders.
Set the Windows User and Password and set AuthScheme to "NTLM".
To authenticate with Kerberos, set AuthScheme to NEGOTIATE. To use Kerberos delegation, set AuthScheme to KERBEROSDELEGATION. If needed, provide the User, Password, and KerberosSPN. By default, the data provider attempts to communicate with the SPN at the specified Url.
By default, the data provider attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats.
You can then access any cube as a relational table: When you connect the data provider retrieves SSAS metadata and dynamically updates the table schemas. Instead of retrieving metadata every connection, you can set the CacheLocation property to automatically cache to a simple file-based store.
See the Getting Started section of the CData documentation, under Retrieving Analysis Services Data, to execute SQL-92 queries to the cubes.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
Having configured both the Tableau Bridge and Tableau Cloud to enable live data connections, you can now publish your workbook to Tableau Cloud. From the Server menu, select Publish Workbook.
👁 Deployment of a workbook containing a live data source. (Salesforce is shown.)After choosing the workbook name and project that you wish to publish to, configure the deployment so that the CData ODBC driver for SQL Analysis Services is embedded in your workbook as a separate, live data source.
The published workbook now updates alongside the underlying SQL Analysis Services data. From a published dashboard, simply click the Refresh button to reflect the most recent changes.
Download a free trial of the SQL Analysis Services ODBC Driver to get started:
Download NowLearn more:
👁 SQL Server Analysis Services IconThe SQL Analysis Services ODBC Driver is a powerful tool that allows you to connect with live data from SQL Analysis Services, directly from any applications that support ODBC connectivity.
Access Analysis Services report data like you would a database, through a standard ODBC Driver interface. Supports Direct Query and MDX query capabilities.