How Often Does Tableau Live Connection Refresh?

When you need up-to-the-minute data, Tableau's live connections seem like the perfect solution. But if you've ever used them, you might have found yourself asking, "How often is this actually refreshing?" This article will get straight to the bottom of how Tableau's live connections work, what "refresh" really means in this context, and what factors influence how fresh your data truly is.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Understanding the Two Main Connection Types: Live vs. Extract

Before we dive into the details of refresh rates, it's important to understand the fundamental difference between Tableau's two data connection options: Live and Extract. Your choice between them is one of the most significant decisions you'll make when building a dashboard, as it directly impacts performance and data freshness.

What is a Live Connection?

A live connection means that Tableau is querying the source database directly every time you interact with a visualization. Think of it as an open phone line to your data. When you change a filter, select a new date range, or even just load a dashboard, Tableau sends a query to the database, which then sends the results back to be visualized. This is ideal when you need to see data in real-time or near-real-time, as it always reflects the current state of your data source.

What is a Tableau Extract?

A Tableau Extract, on the other hand, is a compressed snapshot of the data that is imported and stored within Tableau's high-performance data engine. Instead of querying the source database every time, Tableau queries this local, optimized copy. This almost always results in faster dashboard performance because the data is pre-processed and ready for quick analysis. However, since it's a snapshot, the data is only as fresh as the last scheduled refresh. You might schedule your extract to refresh every hour, every day, or once a week, depending on your needs.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Key Differences at a Glance

• Data Freshness: Live connections offer real-time data from the source, while extracts are point-in-time snapshots.
• Performance: Extracts are typically much faster because they query a pre-optimized .hyper file. Live connections are limited by the speed and workload of the source database.
• Database Load: Live connections put a constant load on your source database. Every user interaction generates a new query. Extracts put a load on the database only during the scheduled refresh time.

How Often Does a Live Connection Actually Refresh?

This is the central question, and the answer is simpler than you might think: a live connection refreshes whenever you ask it to. It's not on a timer or a fixed schedule. The refresh is triggered by user interaction.

Here's a breakdown of what that means in practice:

• Opening a Workbook or View: The moment you open a dashboard with a live connection, Tableau sends one or more queries to the data source to fetch the data needed for the initial view.
• Changing a Filter: If you select a different region, product category, or time period from a filter, Tableau generates and sends a new query reflecting that change. For instance, filtering from "All Regions" to "West" would translate a query from SELECT SUM(Sales) FROM Orders to SELECT SUM(Sales) FROM Orders WHERE Region = 'West'.
• Drilling Down or Up: Clicking a "+" to expand a hierarchy (e.g., from year to quarter) sends a new query to get that more granular data.
• Using Parameters: Adjusting a parameter that influences a calculation or filter will also trigger a new query to the database.
• Manual Refresh Click: Explicitly clicking the "Refresh" button in the toolbar forces Tableau to send new queries for all worksheets in the dashboard.

In short, there is no automatic, background refresh every five minutes. The "liveness" of the connection refers to Tableau's ability to query the operational database on-demand, not its ability to push updates to you automatically.

The Critical Role of Caching

If live connections query the database with every interaction, why does it sometimes feel like the data isn't perfectly up-to-date? The answer is caching.

To improve speed and reduce the load on your database, both Tableau Desktop and Tableau Server/Cloud use multiple layers of caching. A cache is a temporary storage area where Tableau keeps the results of recent queries. When you or another user performs an action that results in the exact same query being sent again within a short period, Tableau can often serve the results from its cache instead of hitting the database again.

For example, imagine you have a dashboard showing total sales.

• User A opens the dashboard at 9:00 AM. Tableau queries the database and caches the result for "total sales."
• User B opens the same dashboard at 9:01 AM. If the cache is still valid, Tableau might show User B the cached result from 9:00 AM instead of querying the database again. A new sale made at 9:00:30 AM might not be visible to User B immediately.

This is where the manual "Refresh" button becomes your best friend. Clicking this button tells Tableau to ignore its cache and go directly to the source database for fresh data.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Controlling the Cache on Tableau Server/Cloud

Tableau Server and Cloud administrators have control over caching behavior. When publishing a workbook, you can configure the data connection's cache settings with options like:

• Refresh More Often: This setting forces Tableau to bypass the cache and query the source database more frequently, ensuring greater data freshness at the cost of performance and database load. This is the best option for truly operational, real-time dashboards.
• Refresh Less Often: This tells Tableau to hold onto cached data for longer, prioritizing performance over freshness. It's useful for dashboards where the underlying data doesn't change much.
• Balanced: This is the default setting, letting Tableau decide based on its own internal logic when to serve from cache versus when to query the source.

For most users, knowing that the "Refresh" button forces a bypass of the cache is the most important takeaway. If you ever doubt the freshness of your data on a live connection, just hit refresh.

Key Factors that Affect Live Connection Performance

A fast dashboard with a live connection has less to do with Tableau and more to do with the health of the underlying data source. Any performance issues will be magnified because every user action can trigger a new query. Several factors influence how quickly your dashboards will load and respond:

1. Database Performance

Is your database optimized for analytical queries? Is it already strained by handling transactional requests from your primary application? Connecting Tableau to a slow or overburdened database is the most common cause of slow live dashboards. Best practice is to connect to a dedicated reporting database, a read replica, or a data warehouse like Snowflake, BigQuery, or Redshift, which are designed for fast analytical queries.

2. Query Complexity

Complex calculations, a large number of filters, intricate table joins, and level-of-detail (LOD) expressions in your worksheet all contribute to the complexity of the SQL query Tableau generates. The more complex the query, the longer the database will take to execute it.

3. Network Latency

The physical or virtual distance between your Tableau instance (Desktop or Server) and your database matters. High network latency can add significant delays to an otherwise fast query. A Tableau Server and its database located in the same data center will always be faster than if they are separated across different clouds or countries.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

4. Data Volume

Querying a table with hundreds of millions of rows will naturally be slower than querying one with a few thousand. While live connections can handle huge datasets, performance depends on proper database indexing and optimization to ensure it can return a result quickly.

When Should You Use a Live Connection vs. an Extract?

Now that you understand the mechanics, you can make an informed decision. The right choice depends entirely on your specific use case.

Use a Live Connection When:

• You need true, real-time data. Dashboards for monitoring operations, call center stats, financial market changes, or live event tracking are prime candidates.
• Your database is lightning-fast. If you have an optimized data warehouse, you can get the benefits of real-time data without sacrificing performance.
• Your datasets are massive. For petabyte-scale data, creating an extract might be impractical or impossible.
• Leveraging specific database features. Some organizations use their database's built-in row-level security or proprietary functions, which can only be utilized through a live connection.

Use an Extract When:

• Performance is the highest priority. If you need sub-second dashboard load times, an extract is almost always the answer.
• The source database is slow. Using an extract protects users from poor dashboard performance and reduces the query load on your critical production systems.
• Data changes are infrequent. If the data only updates daily, an extract refreshed every morning is far more efficient than a live connection.
• You need offline access. Extracts allow you to take a packaged workbook with you on a laptop and analyze data without an internet connection.

Final Thoughts

A Tableau live connection doesn't refresh on a set time interval, it sends direct queries to your data source in real-time based on user interactions. The perceived freshness of this data is a balance between these on-demand queries and Tableau's performance-optimizing cache, which you can bypass anytime by hitting the "Refresh" button. Choosing between a live connection and an extract means weighing your needs for instant data freshness against the demand for maximum dashboard performance.

Instead of wrestling with Tableau's live connections, extract schedules, and cache settings, we built Graphed to make getting real-time answers much simpler. We allow you to connect your marketing and sales data sources with a few clicks and ask questions in plain English to instantly see live, interactive dashboards. There's no need to configure complex data connections, we handle the complexity in the background so you can get the business insights you need in seconds, not hours.