Query profiling and optimization in dbt - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is query profiling in dbt?

Query profiling in dbt means checking how long a SQL query takes to run and what parts use the most resources. It helps find slow or costly steps.

beginner

Name one common cause of slow queries in dbt models.

One common cause is missing indexes on columns used in joins or filters, which makes the database scan more data than needed.

intermediate

How can you use dbt to optimize query performance?

You can optimize by breaking big queries into smaller models, using incremental models, and avoiding unnecessary columns or rows in selects.

intermediate

What is the role of the EXPLAIN plan in query optimization?

The EXPLAIN plan shows how the database runs a query step-by-step. It helps find slow parts like full table scans or bad join orders.

beginner

Why is incremental loading useful in dbt for optimization?

Incremental loading updates only new or changed data instead of rebuilding the whole table, saving time and resources.

What does query profiling help you identify in dbt?

A Data quality issues

B Syntax errors in SQL code

C Slow or costly parts of a query

D User access permissions

Query profiling focuses on performance, showing which parts of a query take the most time or resources.

Which dbt feature helps avoid rebuilding entire tables on every run?

A Macros

B Incremental models

C Seeds

D Snapshots

Incremental models update only new or changed data, improving efficiency.

What does the EXPLAIN plan show?

A Query execution steps and costs

B List of tables in the database

C User roles and permissions

D Data schema definitions

EXPLAIN shows how the database runs a query, helping find optimization opportunities.

Which of these can slow down a dbt query?

A Missing indexes on join columns

B Using incremental models

C Selecting only needed columns

D Breaking queries into smaller models

Missing indexes cause the database to scan more data, slowing queries.

What is a good practice to optimize dbt models?

A Use SELECT * in all queries

B Join tables without conditions

C Run all models as full refresh every time

D Avoid selecting unnecessary columns

Selecting only needed columns reduces data processed and speeds up queries.

Explain how you would profile a dbt query and use the results to optimize it.

Think about tools and steps to find and fix slow parts.

Describe the benefits of using incremental models in dbt for query optimization.

Focus on how incremental loading changes the work done.

Practice

1.

What is the main purpose of query profiling in dbt?

easy

A. To write new SQL queries from scratch

B. To create visual dashboards

C. To find slow parts of your data queries

D. To backup your database automatically

Solution

1. Step 1: Understand the goal of query profiling

   Query profiling is used to analyze how queries run and identify slow parts.

2. Step 2: Match the purpose with the options

   Only To find slow parts of your data queries describes finding slow parts, which is the main goal.

3. Final Answer:

   To find slow parts of your data queries -> Option C

4. Quick Check:

   Query profiling = find slow parts [OK]

Hint: Profiling = finding slow query parts fast [OK]

Common Mistakes:

• Confusing profiling with writing queries
• Thinking profiling creates dashboards
• Assuming profiling backs up data

2.

Which of the following is the correct way to run a dbt model named sales_summary from the command line?

easy

A. dbt build sales_summary

B. dbt run --model sales_summary

C. dbt execute sales_summary

D. dbt run model sales_summary

Solution

1. Step 1: Recall dbt command syntax for running models

   The correct command uses 'dbt run --model <model_name>'.

2. Step 2: Compare options with correct syntax

   Only dbt run --model sales_summary matches the correct syntax exactly.

3. Final Answer:

   dbt run --model sales_summary -> Option B

4. Quick Check:

   Run model = dbt run --model [OK]

Hint: Use 'dbt run --model' to run specific models [OK]

Common Mistakes:

• Using 'dbt execute' which is invalid
• Omitting the '--model' flag
• Using wrong command order

3.

Given this dbt model SQL snippet:

select customer_id, count(*) as order_count
from orders
group by customer_id

Which database command helps you understand why this query might be slow?

medium

A. SELECT * FROM orders LIMIT 10

B. DESCRIBE orders

C. SHOW TABLES

D. EXPLAIN SELECT customer_id, count(*) as order_count from orders group by customer_id

Solution

1. Step 1: Identify the tool for query profiling

   The EXPLAIN command shows how the database runs a query and where it may be slow.

2. Step 2: Match EXPLAIN with the given query

   EXPLAIN SELECT customer_id, count(*) as order_count from orders group by customer_id uses EXPLAIN with the query, which helps understand performance.

3. Final Answer:

   EXPLAIN SELECT customer_id, count(*) as order_count from orders group by customer_id -> Option D

4. Quick Check:

   EXPLAIN = query profiling tool [OK]

Hint: Use EXPLAIN before query to profile it [OK]

Common Mistakes:

• Using DESCRIBE which shows table structure only
• Using SHOW TABLES which lists tables
• Running SELECT without profiling

4.

Look at this dbt model SQL snippet:

select * from orders where order_date = '2023-01-01'

After profiling, you see a full table scan causing slowness. What is the best fix?

medium

A. Add an index on the order_date column

B. Remove the where clause

C. Select only order_id column

D. Change order_date to order_id in where clause

Solution

1. Step 1: Understand cause of full table scan

   Full table scans happen when no index supports the filter condition.

2. Step 2: Choose optimization to speed up filtering

   Adding an index on order_date helps the database find rows faster.

3. Final Answer:

   Add an index on the order_date column -> Option A

4. Quick Check:

   Index on filter column = faster queries [OK]

Hint: Index columns used in WHERE to avoid full scans [OK]

Common Mistakes:

• Removing WHERE loses filtering purpose
• Selecting fewer columns doesn't fix scan
• Changing filter column arbitrarily

5.

You have a dbt model joining two large tables:

select c.customer_id, sum(o.amount) as total
from customers c
join orders o on c.customer_id = o.customer_id
group by c.customer_id

Profiling shows the join is slow. Which optimization is best?

hard

A. Ensure both customer_id columns are indexed

B. Remove the GROUP BY clause

C. Replace join with a subquery

D. Add a LIMIT 10 to the query

Solution

1. Step 1: Identify cause of slow join

   Joins on large tables are slow if join keys lack indexes.

2. Step 2: Apply indexing to join keys

   Indexing customer_id on both tables speeds up join operations.

3. Final Answer:

   Ensure both customer_id columns are indexed -> Option A

4. Quick Check:

   Index join keys = faster joins [OK]

Hint: Index join keys to speed up large table joins [OK]

Common Mistakes:

• Removing GROUP BY changes query meaning
• Using subqueries may not improve speed
• Adding LIMIT only reduces output, not join speed