Materialized views for repeated queries in Snowflake - Commands & Configuration

Introduction

When you run the same query many times, it can slow down your work. Materialized views save the results of these queries so you can get answers faster without running the full query each time.

When you have reports that run the same complex query every day.

When you want to speed up dashboards that show the same data repeatedly.

When you want to reduce the load on your database by avoiding repeated heavy queries.

When you want to keep a snapshot of data that updates automatically as the source data changes.

Commands

This command creates a materialized view named mv_sales_summary that stores the total sales per region. It saves the query result so future queries run faster.

Terminal

CREATE MATERIALIZED VIEW my_schema.mv_sales_summary AS SELECT region, SUM(amount) AS total_sales FROM my_schema.sales GROUP BY region;

Expected Output

Materialized view MY_SCHEMA.MV_SALES_SUMMARY successfully created.

This command queries the materialized view to get the precomputed total sales by region quickly.

Terminal

SELECT * FROM my_schema.mv_sales_summary;

Expected Output

REGION   | TOTAL_SALES

---------|------------

East     | 15000

West     | 12000

North    | 18000

South    | 13000

This command manually refreshes the materialized view to update its data with the latest changes from the sales table.

Terminal

ALTER MATERIALIZED VIEW my_schema.mv_sales_summary REFRESH;

Expected Output

Materialized view MY_SCHEMA.MV_SALES_SUMMARY refresh started.

This command deletes the materialized view when it is no longer needed to free up space and resources.

Terminal

DROP MATERIALIZED VIEW my_schema.mv_sales_summary;

Expected Output

Materialized view MY_SCHEMA.MV_SALES_SUMMARY successfully dropped.

Key Concept

If you remember nothing else from this pattern, remember: materialized views store query results to speed up repeated data retrieval.

Common Mistakes

Creating a materialized view without grouping or aggregation on large tables.

This can cause the materialized view to be very large and slow to refresh, defeating the purpose of speeding up queries.

Use materialized views for queries that aggregate or filter data to keep the stored results manageable and efficient.

Not refreshing the materialized view after source data changes.

The materialized view will show outdated data, leading to incorrect query results.

Schedule automatic or manual refreshes to keep the materialized view data current.

Using materialized views for queries that change very frequently with small updates.

Frequent refreshes can cause overhead and reduce performance benefits.

Use materialized views for queries where data changes are less frequent or where eventual consistency is acceptable.

Summary

Create a materialized view to save the results of a repeated query.

Query the materialized view to get faster results than running the full query each time.

Refresh the materialized view to keep data up to date.

Drop the materialized view when it is no longer needed.

Practice

1. What is the main benefit of using a materialized view in Snowflake for repeated queries?

easy

A. It allows users to write queries without SQL knowledge.

B. It automatically deletes old data to save storage space.

C. It encrypts data to improve security during queries.

D. It stores the query results physically to speed up repeated queries.

Solution

1. Step 1: Understand what a materialized view does

   A materialized view saves the results of a query physically, unlike a normal view which runs the query every time.

2. Step 2: Identify the benefit for repeated queries

   Since the results are saved, repeated queries run faster because they read stored data instead of recalculating.

3. Final Answer:

   It stores the query results physically to speed up repeated queries. -> Option D

4. Quick Check:

   Materialized view = stored results for speed [OK]

Hint: Materialized views save query results for faster repeated access [OK]

Common Mistakes:

• Confusing materialized views with normal views
• Thinking materialized views automatically delete data
• Assuming materialized views improve security by encryption

2. Which of the following is the correct syntax to create a materialized view in Snowflake?

easy

A. CREATE MATERIALIZED my_view VIEW AS SELECT * FROM sales;

B. CREATE VIEW MATERIALIZED my_view AS SELECT * FROM sales;

C. CREATE MATERIALIZED VIEW my_view AS SELECT * FROM sales;

D. CREATE VIEW my_view MATERIALIZED AS SELECT * FROM sales;

Solution

1. Step 1: Recall Snowflake syntax for materialized views

   The correct syntax starts with CREATE MATERIALIZED VIEW followed by the view name and query.

2. Step 2: Match syntax with options

   CREATE MATERIALIZED VIEW my_view AS SELECT * FROM sales; matches the correct order and keywords exactly.

3. Final Answer:

   CREATE MATERIALIZED VIEW my_view AS SELECT * FROM sales; -> Option C

4. Quick Check:

   CREATE MATERIALIZED VIEW = correct syntax [OK]

Hint: Materialized views start with CREATE MATERIALIZED VIEW [OK]

Common Mistakes:

• Mixing order of keywords 'MATERIALIZED' and 'VIEW'
• Placing MATERIALIZED after VIEW keyword
• Using incorrect keyword order causing syntax errors

3. Given a materialized view created as CREATE MATERIALIZED VIEW mv_sales AS SELECT region, SUM(amount) AS total FROM sales GROUP BY region;, what will be the result of SELECT * FROM mv_sales WHERE region = 'West'; if the sales table has 3 rows for 'West' with amounts 100, 200, and 300?

medium

A. Empty result set

B. [{"region": "West", "total": 600}]

C. [{"region": "West", "total": 100}]

D. [{"region": "West", "total": 300}]

Solution

1. Step 1: Understand the materialized view query

   The view groups sales by region and sums the amount for each region.

2. Step 2: Calculate sum for 'West' region

   Amounts 100 + 200 + 300 = 600, so total for 'West' is 600.

3. Final Answer:

   [{"region": "West", "total": 600}] -> Option B

4. Quick Check:

   Sum amounts for region 'West' = 600 [OK]

Hint: Sum grouped amounts to find materialized view result [OK]

Common Mistakes:

• Selecting single amount instead of sum
• Ignoring GROUP BY effect
• Expecting empty result when data exists

4. You created a materialized view but notice it returns outdated data after updates to the base table. What is the best way to fix this in Snowflake?

medium

A. Snowflake automatically refreshes the materialized view in the background.

B. Drop and recreate the materialized view every time data changes.

C. Run VACUUM command on the materialized view.

D. Restart the Snowflake warehouse to update the view.

Solution

1. Step 1: Identify how to update materialized views

   Snowflake materialized views are automatically and continuously refreshed in the background when base tables change. Temporary staleness is normal due to refresh latency.

2. Step 2: Use the correct behavior

   Snowflake handles refreshes automatically--no manual command needed.

3. Final Answer:

   Snowflake automatically refreshes the materialized view in the background. -> Option A

4. Quick Check:

   Snowflake MV = automatic background refresh [OK]

Hint: Snowflake automatically refreshes materialized views [OK]

Common Mistakes:

• Unnecessarily dropping and recreating the view
• Using VACUUM which is for table maintenance
• Restarting warehouse does not trigger refresh

5. You want to optimize a dashboard that runs a complex query repeatedly on a large sales table. Which approach using materialized views is best to improve performance while keeping data reasonably fresh?

hard

A. Create a materialized view with aggregated data and schedule periodic refreshes during low-usage hours.

B. Create a materialized view without aggregation and never refresh it.

C. Use a normal view instead of a materialized view to always get fresh data.

D. Create multiple materialized views with full data copies for each query variation.

Solution

1. Step 1: Consider performance and freshness needs

   Aggregated data reduces size and speeds queries; periodic refresh balances freshness and cost.

2. Step 2: Evaluate options for dashboard optimization

   Create a materialized view with aggregated data and schedule periodic refreshes during low-usage hours. uses aggregation and scheduled refresh, best for performance and reasonable freshness.

3. Final Answer:

   Create a materialized view with aggregated data and schedule periodic refreshes during low-usage hours. -> Option A

4. Quick Check:

   Aggregate + scheduled refresh = best practice [OK]

Hint: Aggregate data and refresh periodically for dashboard speed [OK]

Common Mistakes:

• Not refreshing materialized views causing stale data
• Using normal views which are slower for repeated queries
• Creating many full-copy views wasting storage