Comprehensive and Detailed Explanation From Exact Extract:
In Tableau Performance Recording, ''Executing Query'' refers to the amount of time Tableau spends executing the SQL or hyper query generated by the workbook. When an extract is used, the query is executed against the .hyper extract, not the original database.
Tableau documentation identifies several causes of slow query execution within extracts, including:
Nested row-level calculations
Complex logic in calculated fields
Multiple Levels of Detail (LOD) expressions
Non-optimized expressions that force Tableau to compute additional temporary tables
These directly increase query complexity and cause longer ''Executing Query'' durations.
Therefore, optimizing the query requires simplifying or replacing:
Nested calculations
Unnecessary LOD expressions
Complex expressions that increase the workload on the extract engine
Option A is incorrect because the number of VizQL processes affects concurrency, not query execution time.
Option B is partially relevant, but dashboard filters affect the overall workload, not the specific query complexity. If the performance recording shows ''Executing Query'' as the slow section, the query itself (not the filter UI layer) is the problem.
Option D does not apply because extracts use the hyper engine, not the underlying database. Optimizing the original database structure does not change the extract query execution time.
Thus, the consultant should focus on simplifying nested calculations and LODs to reduce extract query complexity.
Tableau Performance Recording guide describing ''Executing Query'' as dependent on calculation complexity.
Tableau extract engine documentation explaining that nested logic, multiple LODs, and granular calculations generate slower extract queries.
Best practices recommending simplification of calculated fields to improve extract query performance.
