Query performance tuning in Tableau - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of query performance tuning in Tableau?

The main goal is to make Tableau dashboards and reports load faster by optimizing how data queries are run.

beginner

Name one common cause of slow queries in Tableau.

Using large data sources without filters or aggregations can cause slow queries because Tableau has to process too much data.

intermediate

How does using extracts instead of live connections help with query performance?

Extracts store a snapshot of data optimized for fast reading, reducing the time Tableau takes to run queries compared to live connections.

intermediate

What is the Tableau Performance Recorder used for?

It records how long each step in loading a dashboard takes, helping you find slow queries or actions to improve.

beginner

Why should you limit the number of quick filters in Tableau dashboards?

Because each quick filter can add extra queries or processing, too many can slow down dashboard performance.

Which of these improves Tableau query performance the most?

A Using data extracts instead of live connections

B Adding more quick filters

C Increasing dashboard size with many sheets

D Using unindexed data sources

Data extracts are optimized for fast queries, unlike live connections which query the source each time.

What does Tableau's Performance Recorder help you find?

A Data refresh schedules

B Slow loading steps in dashboards

C User login times

D Data source connection errors

Performance Recorder tracks how long each dashboard action takes to identify slow parts.

Why can too many quick filters slow down Tableau dashboards?

A They reduce data source size

B They cache data locally

C They improve data aggregation

D They increase the number of queries Tableau runs

Each quick filter can trigger extra queries, increasing load time.

Which practice helps reduce query time in Tableau?

A Adding many complex calculated fields

B Using all data without filters

C Filtering data at the source before loading

D Using live connections for all data

Filtering data early reduces the amount Tableau needs to process.

What is a sign that a Tableau dashboard query is slow?

A Dashboard takes a long time to load

B Dashboard shows data instantly

C Filters update immediately

D Data source connection is offline

Slow queries cause dashboards to load slowly.

Explain three ways to improve query performance in Tableau dashboards.

Think about how data size and query complexity affect speed.

Describe how Tableau's Performance Recorder helps with query performance tuning.

It’s a tool to find where delays happen.

Practice

1. What is the primary purpose of using Tableau's Performance Recorder?

easy

A. To schedule data refreshes

B. To identify slow queries and dashboard actions for optimization

C. To export data to Excel

D. To create new visualizations automatically

Solution

1. Step 1: Understand Performance Recorder's role

   Performance Recorder tracks how long queries and dashboard actions take to run.

2. Step 2: Identify its main use

   This helps users find slow parts to improve dashboard speed.

3. Final Answer:

   To identify slow queries and dashboard actions for optimization -> Option B

4. Quick Check:

   Performance Recorder = Identify slow parts [OK]

Hint: Performance Recorder finds slow dashboard parts fast [OK]

Common Mistakes:

• Thinking it creates visualizations
• Confusing it with data export tools
• Assuming it schedules refreshes

2. Which of the following is the correct way to enable Performance Recorder in Tableau?

easy

A. Use the Data menu to activate Performance Recorder

B. Right-click on a worksheet and select 'Enable Performance Recorder'

C. Click on Dashboard > Performance Settings > Enable

D. Go to Help > Settings and Performance > Start Performance Recording

Solution

1. Step 1: Locate Performance Recorder in Tableau menus

   Performance Recorder is started from the Help menu under Settings and Performance.

2. Step 2: Confirm correct menu path

   The correct path is Help > Settings and Performance > Start Performance Recording.

3. Final Answer:

   Go to Help > Settings and Performance > Start Performance Recording -> Option D

4. Quick Check:

   Performance Recorder start = Help menu [OK]

Hint: Performance Recorder starts from Help menu [OK]

Common Mistakes:

• Looking under Data or Dashboard menus
• Right-clicking worksheet expecting option
• Assuming a separate settings panel

3. Consider a Tableau dashboard with many filters applied on live data. Which change is most likely to improve query performance?

medium

A. Replace live connection with an extract

B. Add more filters to narrow data further

C. Use complex calculated fields for filtering

D. Increase the number of worksheets in the dashboard

Solution

1. Step 1: Understand impact of live connections

   Live connections query the database every time, which can be slow with many filters.

2. Step 2: Use extracts to improve speed

   Extracts store data locally and speed up queries by reducing database load.

3. Final Answer:

   Replace live connection with an extract -> Option A

4. Quick Check:

   Extracts speed queries better than live connections [OK]

Hint: Use extracts to speed up slow live queries [OK]

Common Mistakes:

• Adding more filters increases query time
• Complex calculations slow performance
• More worksheets increase load, not reduce

4. You notice your Tableau dashboard is slow. You see this calculation: IF [Sales] > 1000 THEN [Profit] ELSE 0 END. What is a likely fix to improve performance?

medium

A. Replace the calculation with a simple filter on Sales > 1000

B. Add more nested IF statements

C. Use a string function instead of IF

D. Remove all filters from the dashboard

Solution

1. Step 1: Analyze calculation impact

   Calculations inside dashboards can slow queries, especially row-by-row IF statements.

2. Step 2: Simplify by filtering data first

   Filtering data before calculations reduces rows processed and speeds performance.

3. Final Answer:

   Replace the calculation with a simple filter on Sales > 1000 -> Option A

4. Quick Check:

   Filtering before calculation improves speed [OK]

Hint: Filter data before calculations to boost speed [OK]

Common Mistakes:

• Adding more IFs increases complexity
• Using string functions unrelated to numeric filters
• Removing filters can increase data load

5. A Tableau dashboard uses multiple data sources with complex joins and many filters. Performance is poor. Which combined approach best improves query speed?

hard

A. Increase dashboard size and add more worksheets

B. Keep live connections but add more calculated fields

C. Use extracts for data sources, reduce filters, and simplify joins

D. Remove extracts and rely only on live data

Solution

1. Step 1: Identify performance bottlenecks

   Complex joins and many filters slow queries, especially on live data sources.

2. Step 2: Apply combined fixes

   Using extracts reduces database load, fewer filters reduce query complexity, and simpler joins speed data retrieval.

3. Step 3: Avoid opposite actions

   Adding calculated fields or more worksheets increases load; removing extracts loses speed benefits.

4. Final Answer:

   Use extracts for data sources, reduce filters, and simplify joins -> Option C

5. Quick Check:

   Extracts + fewer filters + simple joins = faster queries [OK]

Hint: Combine extracts, fewer filters, simpler joins for best speed [OK]

Common Mistakes:

• Adding more calculated fields slows performance
• Increasing dashboard size adds load
• Removing extracts loses caching benefits