How to Publish Tableau Dashboard with Live Connection

Publishing a Tableau dashboard with a live data connection eliminates the need for manual refreshes, giving your team access to the most current information. This article walks you through the difference between live connections and extracts, how to publish a dashboard with a live connection, and how to troubleshoot common issues when they pop up.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Live Connection vs. Extract: Which Should You Choose?

In Tableau, you have two primary ways to connect to your data: Live or Extract. Choosing the right one depends entirely on your goals, your data source's performance, and how frequently your data needs to be updated.

What is a Live Connection?

A live connection queries your source database directly. When someone opens your dashboard or interacts with a filter, Tableau sends a query to the database and displays the results in real-time. Think of it as a transparent window directly into your data warehouse or database.

• Pros:
• Cons:

When to use a Live Connection: Use a live connection when real-time or near-real-time data is essential for decision-making and your underlying database is optimized to handle query volume quickly.

What is an Extract?

An extract is a snapshot of your data that is imported, compressed, and stored in Tableau's high-performance, in-memory data engine (.hyper files). Instead of querying your live database, Tableau queries this local, optimized copy.

• Pros:
• Cons:

When to use an Extract: Use an extract when dashboard performance is a top priority, the source database can't support a high query load, or when minute-by-minute data updates aren't necessary for your analysis.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Before You Publish: Key Prerequisites

Before you hit the "Publish" button, a little preparation goes a long way. Ensuring a successful publish for a live connection involves checking three main things: database credentials, network accessibility, and user permissions.

Database Credentials

Tableau Server or Tableau Cloud needs a way to log into your database to run queries. This means it needs a valid username and password. The best practice is to use a dedicated "service account" for Tableau - a database user with only read-only permissions for the specific tables or schemas your dashboard needs. Avoid using your personal credentials, as you'd have to update them every time you change your password.

Network Access

Your Tableau Server instance must be able to communicate with your database over the network.

• Tableau Server & Database On-Premise: If both are on your company's internal network, you'll need to make sure any firewalls allow traffic between the Tableau Server machine and the database server on the designated port (e.g., port 1433 for SQL Server).
• Publishing to Tableau Cloud from an On-Premise Database: If your database is behind a company firewall but you want to publish to Tableau Cloud, you cannot establish a direct live connection. In this scenario, Tableau provides a tool called Tableau Bridge. Bridge is a client that runs on a machine inside your network, acting as a secure "bridge" that maintains the connection between your on-premise data and your Tableau Cloud site. Bridge allows for scheduled extract refreshes and, for some sources, can enable live connections by proxying queries.
• Cloud Databases: If both Tableau and your database are in the cloud (e.g., Snowflake, BigQuery, Amazon Redshift), you just need to ensure your database's firewall rules are configured to accept connections from Tableau Cloud's IP address range.

Permissions

Confirm two types of permissions:

1. Tableau Permissions: The account you're using to publish from Tableau Desktop must have a Creator or Explorer (Can Publish) site role in Tableau Server/Cloud.
2. Database Permissions: As mentioned, the credentials used by Tableau must have at least 'SELECT' (read) permissions on all the tables, views, and schemas that are part of your data source.

How to Publish Your Tableau Dashboard with a Live Connection

Once you've sorted out the prerequisites, publishing the dashboard itself is a straightforward process.

Step 1: Connect to Your Data and Select "Live"

In Tableau Desktop, open a new workbook. On the Connect pane, select your data source. In the connection window, enter your server details and credentials. Before you move on to building, you'll see a choice in the top right corner for Connection: Live vs. Extract. Make sure you select Live. This tells Tableau to query the database directly instead of creating a copy.

Step 2: Build Your Dashboard

Go ahead and build your worksheets and arrange them into a polished dashboard. This part of the process is the same for both live connections and extracts. When your masterpiece is complete, you're ready to share it.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step 3: Begin the Publishing Process

From the top menu in Tableau Desktop, navigate to Server > Publish Workbook.... If you're not already signed in to your Tableau Server or Cloud site, you'll be prompted to do so. This will open the 'Publish Workbook' dialog box, where you'll configure how your dashboard will be shared.

Step 4: Configure Data Source Authentication

This is the most important step for a successful live connection. In the publish dialog, you'll see a section for Data Sources. Click on the Edit link next to your data source. This opens the Authentication settings.

You'll see a dropdown menu with a few options. The most common are:

• Prompt User: This is generally a poor choice for dashboards intended for wide use. Anyone opening the workbook will be asked to enter their own database credentials.
• Embedded Password: This is the most common and effective method for live connections. It stores the service account's database credentials securely on Tableau Server. When a user opens the dashboard, Tableau Server uses these embedded credentials to run the queries on their behalf. You simply select this option and confirm, and Tableau will take care of the rest.
• Server Run As Account or OAuth: Depending on your data source and server configuration, you might see other options like these. For cloud sources like Google BigQuery or Snowflake, setting up and using a saved OAuth connection is often the best choice.

Choose Embedded Password for most standard databases like SQL Server, PostgreSQL, or MySQL unless your organization uses a different authentication standard.

Step 5: Finalize and Publish

After setting up authentication, fill out the rest of the publishing options:

• Project: Choose the destination folder on your server.
• Name: Give your workbook a clear, descriptive name.
• Sheets: Select only the dashboards and worksheets you want others to see. It's good practice to only publish dashboards and hide the individual sheets from view.

Click the big blue Publish button. Once complete, Tableau will open a browser window with your newly published dashboard. Test it out! Click on a filter or a data point. If the view updates without error, your live connection is working perfectly.

Troubleshooting Common Live Connection Issues

Even with careful planning, things can sometimes go wrong. Here are a few common problems and how to solve them.

Issue #1: Dashboard errors out with a connection failure message.

This almost always points to a problem with network connectivity between your Tableau Server/Cloud and your database. Check your firewall rules to make sure the connection isn't being blocked. If using Tableau Cloud with an on-premise source, confirm that the Tableau Bridge client is installed, running, and properly linked to your site.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Issue #2: "Invalid username or password" or authentication errors.

This means the credentials Tableau is using are wrong. This can happen if the service account's password was changed or if you made a typo when embedding them. To fix it, go to the Data Source tab in Tableau Server/Cloud, find your data source, and edit the Connection settings to enter the correct username and password. Alternatively, you can re-publish the workbook from Tableau Desktop with the correct credentials.

Issue #3: The dashboard is extremely slow.

Slow performance isn't an "error," but it's a critical usability problem. With live connections, the bottleneck is almost always the database. Work with your database administrators to see if queries can be optimized with things like database indexing. In Tableau itself, you can improve performance by reducing the number of filters, using context filters, and simplifying complex calculations. If optimization efforts still leave the dashboard too slow, it might be a sign that this specific workbook is a better candidate for an extract, even if it has to be refreshed every 15 or 30 minutes.

Final Thoughts

Publishing your Tableau dashboard with a live connection is the best way to deliver real-time insights across your organization. Once you get the hang of configuring authentication and verifying network connectivity, you'll be automating your most important operational reports with ease.

Our goal with Graphed is to make this process even simpler. Connecting your marketing and sales data sources is a one-click process, and your dashboards are live and fully real-time by default — no need to manage server settings or choose between live connections and extracts. We automate the entire pipeline, letting you ask questions in plain English and get stunning, always-updated dashboards in seconds, so you can focus on insights instead of infrastructure.