Master Tableau From Scratch

Learn Tableau fundamentals, data connections, data preparation, filtering, data modeling, calculations, LOD expressions, visualizations, dashboards, and storytelling through structured practical lessons.

COURSE SYLLABUS

Live vs Extract Connections

Understand the two major ways Tableau works with connected data. Learn how Live Connections access source data and how Extract Connections use stored snapshots for analysis. Explore their differences, refresh options, advantages, limitations, and practical use cases.

1. Introduction to Live and Extract Connections

Tableau provides different connection approaches for working with data sources. Two important approaches are Live Connections and Extract Connections.

A Live Connection sends queries to the underlying data source when Tableau needs data for a view. An Extract Connection works with a stored snapshot of data that Tableau has extracted from the original source.

What You Will Learn

  • Understand Live Connections.
  • Understand Tableau Extracts.
  • Learn how both connection types work.
  • Compare Live and Extract Connections.
  • Understand extract refresh operations.
  • Explore performance and data freshness considerations.
  • Choose the appropriate connection for business scenarios.

2. What Is a Live Connection?

A Live Connection allows Tableau to query the underlying data source when a user interacts with a visualization or requests data.

Instead of relying on a stored extract as its primary data representation, Tableau sends queries to the connected source. The source processes those queries and returns the requested results.

How Live Connections Work

  1. Tableau connects to a supported database or data source.
  2. The user creates a worksheet or visualization.
  3. Tableau sends the required query to the source.
  4. The data source processes the query.
  5. The results are returned to Tableau.
  6. Tableau displays the updated visualization.

Advantages of Live Connections

  • Can provide access to current source data when queries execute.
  • A separate Tableau extract does not need to be maintained.
  • Suitable for data sources that require centralized control.
  • Can work well with databases optimized for analytical queries.
  • Useful when source-side updates need to be reflected in analysis.

Limitations of Live Connections

  • Performance depends on the source system and network.
  • Complex queries may increase database workload.
  • Network interruptions can affect access to data.
  • Database permissions and availability are important.
  • High user activity can increase query demand on the source.
Example: A financial analyst monitors transaction information stored in a database. A Live Connection can help the analyst query the current source data when opening or interacting with a Tableau report.

3. Live Connection Architecture

In a Live Connection, Tableau communicates with the original data source to retrieve the results required for a view.

Tableau Worksheet Dashboard Query Request Query Results Database SQL Server MySQL / Oracle Data is queried from the original source

Figure 1: Conceptual architecture of a Tableau Live Connection.

Important: A Live Connection does not guarantee that every view always displays the latest possible record. Results depend on query execution, source updates, caching, and the behavior of the connected system.

4. What Is a Tableau Extract?

A Tableau Extract is a stored snapshot of data created from an original data source. Tableau extracts the selected data and stores it in its extract format so that analysis can use the stored data rather than querying the original source for every interaction.

Extracts are useful when users want to improve workbook responsiveness, work with data offline where supported, or reduce repeated queries against a source system.

How Extract Connections Work

  1. Connect Tableau to the original data source.
  2. Choose the Extract connection option.
  3. Configure the required extract settings.
  4. Run the extract creation process.
  5. Tableau stores the extracted data.
  6. Worksheets use the stored extract for analysis.

Advantages of Extract Connections

  • Can improve performance for many analytical workloads.
  • Can reduce repeated query traffic to the original source.
  • Supports working with stored data when the original source is unavailable, subject to the product and workbook setup.
  • Allows users to configure full or incremental refreshes where supported.
  • Can be useful for large reporting environments with controlled refresh schedules.

Limitations of Extract Connections

  • Extract data may become outdated until refreshed.
  • Extract creation and refresh require processing resources.
  • Stored extracts consume storage space.
  • Large extracts may require additional memory and disk resources.
  • Refresh configuration and permissions must be managed.
Example: A retail company prepares a daily sales dashboard using an extract refreshed every morning. Managers can analyze the stored data throughout the day without repeatedly querying the original database.

5. Extract Connection Architecture

With an Extract Connection, Tableau first retrieves data from the original source and creates a stored extract. The workbook then uses the extract for analysis.

Original Source Database Excel / CSV Extract Creation Process Stored Extract .hyper file Stored Data Tableau Analysis Views Refresh when updated source data is required Tableau analyzes the stored extract until it is refreshed.

Figure 2: Conceptual architecture of a Tableau Extract Connection.

6. Live vs Extract: Key Differences

Both connection types help users analyze data, but they differ in how data is accessed, stored, refreshed, and maintained.

Comparison Live Connection Extract Connection
Data Access Queries the original data source. Uses stored extracted data.
Data Freshness Can reflect current source data when queries execute. Depends on the last successful extract refresh.
Storage Does not require a separate extract for the connection. Requires storage for the extract.
Performance Depends on source performance, query complexity, and network. Can improve responsiveness for suitable workloads.
Network Dependency Generally requires access to the source when queries execute. Can use stored data without continuous source access, subject to workbook configuration.
Refresh Source data is queried as needed. Requires full or incremental refresh as configured.
Database Workload Queries are sent to the source. Source is accessed during extract creation and refresh.
Typical Usage Source-driven and frequently changing analysis. Scheduled reporting and stored analytical datasets.
Remember: An Extract is not automatically faster in every situation. Performance depends on extract size, workbook design, calculations, data volume, and the underlying environment.

7. Extract Refresh: Full and Incremental

Extract refresh is the process of updating stored extract data from the original source. Tableau provides different refresh approaches depending on the data source and configuration.

Full Refresh

A Full Refresh rebuilds the extract using the data returned by the configured source query. It replaces the previous extract contents with the refreshed data.

When to Use Full Refresh

  • When existing records may have changed.
  • When records may have been deleted.
  • When a complete rebuild is required.
  • When incremental refresh is not suitable for the source or requirement.

Incremental Refresh

Incremental Refresh adds new records to an existing extract based on a configured field and refresh strategy, where supported.

When to Use Incremental Refresh

  • When new records are regularly added.
  • When a suitable incrementing field is available.
  • When rebuilding the entire extract is unnecessary.
  • When the source and refresh configuration support incremental updates.
Feature Full Refresh Incremental Refresh
Operation Rebuilds the extract. Adds qualifying new records.
Data Coverage Re-reads the configured source data. Focuses on records identified by the incremental configuration.
Processing May require more processing for large datasets. Can reduce processing for suitable append-only workloads.
Changed Records Can capture changes when the refreshed source query returns them. Does not automatically detect every modification to older records.
Important: Incremental refresh is not a universal replacement for full refresh. If older records can be modified or deleted, an incremental strategy based only on new records may leave the extract out of date.

8. Extract Refresh Workflow

Extracts must be refreshed according to business requirements so that stored data remains sufficiently current for reporting.

Source Data New Records Updated Values Refresh Full Refresh Incremental Extract Updated Data Stored Snapshot Dashboard Updated View Analysis Keeping Extract Data Updated Refresh operations update the stored snapshot from the source.

Figure 3: Typical Tableau Extract refresh workflow.

9. When Should You Use Live or Extract?

Choosing the correct connection depends on the business requirement, data freshness, source performance, network availability, and the amount of data being analyzed.

Choose Live Connection When

  • Users need to query current source data frequently.
  • The underlying database can handle the required queries.
  • Source-side security and governance are important.
  • Maintaining a separate extract is not desirable.
  • The data source is reliably accessible.

Choose Extract Connection When

  • Stored data can meet the reporting freshness requirement.
  • Improved responsiveness is important for the workload.
  • Repeated queries should be reduced against the source.
  • Scheduled refreshes are acceptable.
  • Users need to work with stored data in supported scenarios.

Real-World Business Scenarios

Business Scenario Possible Choice Reason
Frequently updated operational reporting Live Queries the original source when views are accessed.
Daily management dashboard Extract A scheduled refresh may meet the reporting requirement.
Large reporting dataset with suitable source support Extract A stored extract may improve responsiveness.
Centralized database with controlled access Live Can keep queries within the source system's access model.
Analysis during periods without source access Extract Stored data may remain available, subject to workbook configuration.
Best Practice: Select the connection type based on measurable requirements. Test performance with realistic data volumes and user activity instead of assuming one connection type is always better.

10. Performance Considerations

Tableau workbook performance is influenced by many factors. Connection type is important, but database performance, data volume, network quality, calculations, and workbook design also affect response times.

Factor Impact Recommended Practice
Data Volume Large datasets can increase processing time. Use appropriate filters and data preparation.
Network Latency Can affect Live Connection query response. Use reliable network infrastructure.
Database Performance Slow source queries can affect visualizations. Optimize database queries and source design.
Extract Size Large extracts can increase storage and refresh costs. Extract only required data when appropriate.
Calculations Complex calculations can increase query or processing work. Review calculations and simplify where possible.
Filters Filter design can affect query execution. Use filters according to the analysis requirement.

11. Common Problems and Troubleshooting

Problem Possible Cause Suggested Solution
Live Connection is slow Slow database queries or network latency. Review source performance and optimize queries.
Database is unavailable Server outage or connectivity issue. Verify server availability and network access.
Extract is outdated Refresh has not run successfully. Check refresh status and execute the required refresh.
Extract refresh fails Credentials, permissions, or source errors. Check connection credentials and refresh logs.
Extract file is large Too many rows or unnecessary fields. Review the extract scope and data requirements.
Incremental refresh misses updates Older records were modified outside the incremental strategy. Review the refresh key and consider a full refresh.
Important: Always verify extract refresh completion and data freshness before publishing business-critical reports.

12. Practical Exercise

Task: Compare Live and Extract Connections

Use a sample Excel or database dataset to explore the two connection approaches in Tableau.

Exercise A: Live Connection

  1. Open Tableau Desktop.
  2. Connect to a supported data source.
  3. Select the Live connection option where available.
  4. Create a worksheet using Sales and Region fields.
  5. Review the visualization and source connectivity.

Exercise B: Extract Connection

  1. Connect to the same supported data source.
  2. Select the Extract connection option.
  3. Configure the extract settings.
  4. Create the extract.
  5. Create a similar worksheet.
  6. Compare the experience with the Live connection.

Exercise C: Refresh the Extract

  1. Review the available extract refresh options.
  2. Understand the difference between full and incremental refresh.
  3. Run an appropriate refresh where supported.
  4. Verify the refreshed data.

13. Practice Questions

Basic Questions

  1. What is a Live Connection in Tableau?
  2. What is a Tableau Extract?
  3. How does a Live Connection work?
  4. Why are Tableau Extracts created?
  5. What is the difference between Live and Extract Connections?
  6. What is an extract refresh?
  7. What is a full refresh?
  8. What is an incremental refresh?

Practical Questions

  1. Create a Live Connection to a supported data source.
  2. Create an Extract Connection.
  3. Compare the two connection approaches.
  4. Review the extract refresh options.
  5. Identify the factors affecting connection performance.
  6. Verify whether an extract has been refreshed successfully.

Interview Questions

  1. Explain Live and Extract Connections in Tableau.
  2. When would you choose a Live Connection?
  3. When would you choose an Extract Connection?
  4. What is the difference between full and incremental refresh?
  5. Does a Live Connection always show real-time data?
  6. How can you improve Tableau workbook performance?
  7. What happens if an extract refresh fails?
  8. What are the limitations of incremental refresh?

14. Summary

In this lesson, we learned about the two important Tableau connection approaches: Live Connections and Extract Connections. A Live Connection queries the original data source, while an Extract Connection works with a stored snapshot of data.

We explored their architectures, advantages, limitations, performance considerations, and business use cases. We also learned about Full Refresh and Incremental Refresh operations used to update Tableau Extracts.

Choosing the correct connection depends on data freshness, source performance, network availability, storage, and reporting requirements. In the next lesson, we will explore Data Fields and Data Types in Tableau.