Query performance tuning in Tableau - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an extract for faster query performance.

Tableau

CREATE EXTRACT [1]

Drag options to blanks, or click blank then click option'

ADATA

BVIEW

CDATABASE

DTABLE

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'DATA' or 'DATABASE' instead of 'TABLE' causes syntax errors.

Trying to extract a VIEW instead of a TABLE may not improve performance as expected.

In Tableau, creating an extract of the TABLE improves query speed by storing data locally.

2fill in blank

medium

Complete the Tableau calculation to optimize query by filtering only recent data.

Tableau

IF [Order Date] >= DATEADD('year', -1, TODAY()) THEN [1] ELSE NULL END

Drag options to blanks, or click blank then click option'

A[Sales]

B[Profit]

C[Quantity]

D[Discount]

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing non-revenue fields like Discount or Quantity may not optimize the main query.

Leaving the blank empty causes calculation errors.

Filtering [Sales] for the last year reduces data scanned, improving query speed.

3fill in blank

hard

Fix the error in the Tableau LOD expression to calculate average sales per customer.

Tableau

{ FIXED [Customer ID] : AVG([1]) }

Drag options to blanks, or click blank then click option'

A[Profit]

B[Quantity]

C[Sales]

D[Discount]

Attempts:

3 left

💡 Hint

Common Mistakes

Using Profit or Quantity changes the meaning of the calculation.

Using Discount does not represent sales amount.

The correct measure to average per customer for sales analysis is [Sales].

4fill in blank

hard

Fill both blanks to optimize query by limiting data and aggregating sales.

Tableau

SUM(IF [Region] = [1] THEN [Sales] ELSE 0 END) / COUNTD([2])

Drag options to blanks, or click blank then click option'

A'West'

B[Customer ID]

C'East'

D[Order ID]

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong region name causes incorrect filtering.

Counting Order ID instead of Customer ID changes the aggregation meaning.

Filtering sales for the 'West' region and counting distinct [Customer ID] optimizes aggregation.

5fill in blank

hard

Fill all three blanks to create a calculated field that improves query speed by filtering and aggregating profit.

Tableau

SUM(IF [Category] = [1] AND [Order Date] > [2] THEN [3] ELSE 0 END)

Drag options to blanks, or click blank then click option'

A'Furniture'

BDATE('2023-01-01')

C[Profit]

D'Technology'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong category or date reduces filter effectiveness.

Summing Sales instead of Profit changes the metric focus.

Filtering for 'Furniture' category and orders after 2023-01-01, then summing [Profit] helps focus queries and improve speed.

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