--- schema_version: "1" id: 56818e2ade8cdb3d0601934787c5f304bf5a573398503beca0333c78b7cd878c title: Publish with Data Connect collection: tableau version: current locale: en-us portal_url: https://docs.salesforce.com/tableau/current/en-us/online/data_connect_publish.md canonical_url: https://help.tableau.com/current/online/en-us/data_connect_publish.htm source_site: help.tableau.com content_type: documentation content_hash: 49a4f89de2234409f1e7c8d2604a764b8487e9e2b175d56637740ef2ef7306ed description: Publish and query private data with Data Connect, including query error troubleshooting. --- [Skip to main content](#main-content) # Publish with Data Connect As of September 2025, Tableau Data Connect is no longer available for new deployments. We recommend that existing customers migrate their Data Connect deployment to [Private Connect](https://help.tableau.com/current/online/en-us/private_connect_migrate_from_bridge.htm) or [Tableau Bridge](https://help.tableau.com/current/online/en-us/data_fresh_sync_section.htm). Data Connect will be retired in the future. Data Connect is a product that is managed by site admins. But it can service queries for all users on a Tableau Cloud Site. Creators who publish content will need to keep a few things in mind when connecting to private network data using Data Connect. Those items are outlined below. Explorers and Viewers will utilize Data Connect, but will largely be unaware of whether or not it is in use. ## Database connectivity Data Connect deploys the Bridge client which services database queries. The Bridge clients used in Data Connect are individual deployments of Tableau Bridge on Linux for Containers. Therefore, Data Connect supports all database connectors and database authentication patterns that Tableau Bridge on Linux for Containers supports. For more information, see [Connectivity with Bridge](https://help.tableau.com/current/online/en-us/to_sync_local_data.htm). Data Connect supports both live and extract data sources. Data Connect only supports database drivers built for Linux. The drivers must be included in the base image that site admins configure during Data Connect setup. ## Using Data Connect to query private data Creators who need to connect to private network data with Data Connect [follow the same process of connecting to data](https://help.tableau.com/current/pro/desktop/en-us/basicconnectoverview.htm) with Tableau Desktop and publishing it to Tableau Cloud. There are two additional steps required for keeping that data fresh with Data Connect: - When setting up Data Connect, site admins create pools. Pools define the database domains that will use Data Connect. Queries to that database domain are sent to the Data Connect Bridge client. - (Published Data Sources only) Data Source owners must take one additional action for each data source after publishing it to Tableau Cloud to use Data Connect. After a data source is published you can rotate the credentials of that data source and update other aspects of the connection information. See [Update Bridge Connection Information](https://help.tableau.com/current/online/en-us/to_sync_client_settings.htm). - **Using embedded data sources**: Data Connect supports querying embedded data sources. There are many advantages to using published data sources to scale centralized data sources. For more information, see [Using Embedded Data Sources](https://help.tableau.com/current/online/en-us/to_bridge_eds.htm). - **Setting up refresh schedules**: Data Connect allows you to schedule refreshes of extract data on a regular basis. See S[Set Up a Private Network Refresh Schedule](https://help.tableau.com/current/online/en-us/to_sync_schedule.htm). - **Managing email alerts**: If enabled by your site admin, you will receive email alerts about refresh failures for all of the data sources that you own. When refreshes for your data sources are managed by Data Connect, the type of alerts you receive, when you receive the alerts, and the alerts that you can configure will differ from Tableau Cloud alerts. See [Manage Email Alerts for Bridge](https://help.tableau.com/current/online/en-us/to_bridge_eds.htm). ## Troubleshooting errors from individual queries Individual jobs are handled by the Data Connect Bridge client. To determine the underlying cause, the troubleshooting steps required will depend on the user scenario. Site admins have access to data about all refresh jobs serviced by Data Connect. For more information on accessing this data, see [Monitoring Data Connect query health](https://help.tableau.com/current/online/en-us/data_connect_admin.htm#Monitori). The Admin Insights Job Performance data source is especially useful in identifying if issues are occurring commonly on the same database or on the same Data Connect Agent. In the event that a node becomes unhealthy, the Bridge clients and the queries they execute can fail. To troubleshoot node health, see [Troubleshooting service initialization and health](https://help.tableau.com/current/online/en-us/data_connect_admin.htm#Troubles). ### Live query errors Live query errors arise when a user opens a dashboard with a live data source configured to use Data Connect. These errors indicate that there is an issue with the connection to the database. For common troubleshooting steps, see [Identifying causes for live query issues](https://help.tableau.com/current/online/en-us/to_bridge_troubleshoot.htm#livequery) . ### Extract refresh failures Data source owners receive email notifications if an extract refresh is unsuccessful. These email notifications will contain error messages that can support troubleshooting the issue. For more information about how Data Source owners can troubleshoot their jobs, see [Identifying causes for scheduled refresh issues](https://help.tableau.com/current/online/en-us/to_bridge_troubleshoot.htm#refresh).