What is a Tableau Extract?

Cody Schneider8 min read

If you've spent any time with Tableau, you've almost certainly seen the choice between a "Live" connection and an "Extract." Picking the right one can be the difference between a lightning-fast dashboard and one that has your users drumming their fingers on the desk. This article breaks down exactly what a Tableau Extract is, when you should use one, and how to set it up.

GraphedGraphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Watch Graphed demo video

Tableau Extract vs. Live Connection: Understanding the Core Difference

To really understand what an extract is, it helps to first understand its alternative: a live connection. The choice you make here dictates how Tableau interacts with your data source, whether that's a simple Excel file, a Google Sheet, or a massive corporate SQL database.

What is a Live Connection?

A live connection is exactly what it sounds like. When you build a chart or apply a filter in your Tableau workbook, Tableau sends a direct query to your underlying data source. The data source processes that query and sends the results back to be visualized.

  • Pros: The data is always in real-time. If a new sale is logged in your database, a live-connected dashboard will show it on the next refresh or interaction.
  • Cons: Performance is completely dependent on the speed of your data source. If you're connecting to a slow, overworked database, your Tableau dashboard will also be slow and overworked.

What is a Tableau Extract (.hyper file)?

A Tableau Extract, on the other hand, is a compressed, optimized snapshot of your data. When you create an extract, Tableau queries your data source once, pulls that data into its own high-performance database engine (called Hyper), and saves it as a local file with a .hyper extension.

From that point on, any work you do in Tableau - filtering, sorting, calculating - happens within this super-fast, optimized file. Tableau is no longer talking to the original data source, it's only talking to the extract.

  • Pros: Drastically improved performance. Dashboards and visualizations load and respond much faster. You can also work on your Tableau workbook offline, as the data is stored on your machine.
  • Cons: The data is static. It's a snapshot in time, only as current as the last time you refreshed the extract. This means it's not suitable for true real-time analysis.

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

When to Use a Tableau Extract: The Big Benefits

Swapping a live connection for an extract can seem like a small click, but its impact is massive. Here are the most common scenarios where using an extract is the best move.

1. To Massively Boost Performance

This is the number one reason to use an extract. Large datasets, slow databases, or connections over a laggy network can bring a live-connected dashboard to a crawl. By creating an extract, you are essentially pre-loading all the necessary data into Tableau's optimized engine. Filtering a dashboard with millions of rows might take several seconds or longer with a live connection, but with an extract, it can feel instantaneous.

Relatable Example: Imagine your company's sales data is stored in a decade-old SQL database that takes forever to run queries. A dashboard built with a live connection will frustrate every user. By creating an extract that refreshes every morning, you give the sales team a high-speed dashboard for their daily analysis without them ever having to wait on the slow database.

2. To Work Offline or Reduce Database Load

Since an extract is a self-contained file saved on your computer, you don't need a network connection to your original data source to work on your dashboard. This is a lifesaver for anyone who travels for work or needs to present a dashboard in a location with unreliable Wi-Fi.

Furthermore, it's a huge favor to your IT and data engineering teams. A dashboard used by dozens of people, each clicking on filters and changing parameters, can send hundreds or thousands of queries to a production database. An extract reduces that conversation to a single query during a scheduled refresh, preventing your analytics work from slowing down critical business operations.

GraphedGraphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Watch Graphed demo video

3. For Predictable, Sharable Snapshots

Sometimes you don't want the data to change. If you're doing an end-of-quarter analysis or building a report on a completed marketing campaign, you want a static snapshot of the data from that specific point in time. An extract captures that moment perfectly. It ensures that everyone reviewing the workbook is looking at the exact same numbers, without the risk of new data coming in and changing the results.

When a Live Connection Is the Better Choice

Extracts are powerful, but they aren't the solution for everything. There are clear situations where a live connection is not just preferable, but necessary.

  • When you need truly real-time data: If you're building a dashboard for operational monitoring - like tracking call center volume, factory floor production, or live inventory levels - you need data that is up to the second. An extract, even one refreshing every 15 minutes, will be too stale.
  • When your data source is already highly optimized: Modern cloud data warehouses like Google BigQuery, Amazon Redshift, and Snowflake are built for speed and can handle heavy analytical workloads. In these cases, a live connection can sometimes be just as fast as an extract, saving you the hassle of managing refresh schedules.
  • When data storage is a concern: Extracts are physical files that take up disk space. For exceptionally large datasets (think billions of rows), the resulting .hyper file can be very large, posing a problem for local storage or server space.

Step-by-Step: Creating Your First Tableau Extract

The good news is that creating an extract is incredibly simple. All it takes is a couple of clicks at the beginning of your data connection setup.

  1. Connect to Your Data: In Tableau Desktop, start by connecting to your data source as you normally would (e.g., Microsoft Excel, Google Sheets, PostgreSQL, etc.).
  2. Select the "Extract" Radio Button: On the Data Source screen (where you can see a preview of your data and drag tables into the canvas), look at the top right corner. You'll see two radio button options: Live and Extract. Simply click on Extract.
  3. Edit your Extract (Optional but Recommended): Next to the radio button, you'll see a link that says "Edit." Clicking this opens a dialog box with powerful options to control the size and scope of your extract. This is a key step for optimizing performance.
  4. Go to a Worksheet: As soon as you click on a worksheet tab (e.g., "Sheet 1"), Tableau will prompt you to choose a location to save your extract file (the .hyper file). Save it, and Tableau will begin the process of creating the extract. Once it's done, you're ready to start building your visualizations at high speed!

Keeping Your Data Fresh: How to Refresh an Extract

Creating an extract is just the first step. To keep it useful, you'll need to refresh it to pull in new data from the source. You have two main ways to do this.

Manual Refreshes in Tableau Desktop

A manual refresh is perfect for when you're actively developing a workbook or just need a quick, ad-hoc update. Simply right-click on your data source in the Data pane on the left side of your screen, navigate to "Extract," and click "Refresh." Tableau will reconnect to the original data source and rebuild the extract with the latest information.

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

Automated Refreshes with Tableau Server or Cloud

This is the "set it and forget it" method. When you publish a workbook with an extract connection to Tableau Server or Tableau Cloud, you are given the option to set up a refresh schedule. You can configure it to update:

  • Every hour
  • Once daily at a specific time (e.g., 5 AM before your team logs in)
  • Once a week or once a month

Setting up a schedule is essential for production dashboards that your team relies on. It ensures they always have reasonably fresh data without anyone needing to manually intervene.

Final Thoughts

Deciding between a live connection and an extract in Tableau comes down to one key tradeoff: real-time data vs. dashboard performance. Extracts are snapshots of your data designed for speed, offline access, and reducing the load on your databases, making them the default choice for most strategic and analytical dashboards. Live connections are for those moments when seeing data in real-time is an absolute necessity.

Figuring out data connections, extracts, and refresh schedules is part of the territory with traditional BI tools. At Graphed, we handle this differently. Instead of making you manage the technical side, we built an AI data analyst that automatically connects to your tools and keeps dashboards updated in real-time. You simply describe the report you want in plain English - like "Show my top ad campaigns by conversion rate this month" - and get a finished, live dashboard in seconds, skipping the setup and getting straight to the insights.

Related Articles