Bird
Raised Fist0
Snowflakecloud~3 mins

Why Querying historical data (AT, BEFORE) in Snowflake? - Purpose & Use Cases

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
The Big Idea

What if you could rewind your data like a video to see exactly what happened before?

The Scenario

Imagine you need to find out what your data looked like last week or last month. You try to dig through backups or old files manually to find the exact version. It feels like searching for a needle in a haystack.

The Problem

Manually searching old backups is slow and confusing. You might miss the right version or make mistakes copying data. It wastes time and can cause errors in reports or decisions.

The Solution

Using Snowflake's ability to query data AT or BEFORE a specific time lets you see exactly how your data looked at that moment. No need to dig through backups or restore files. It's fast, safe, and reliable.

Before vs After
✗ Before
Restore backup from last week; run queries on restored data
✓ After
SELECT * FROM table AT (TIMESTAMP => '2024-05-01 00:00:00')
What It Enables

You can instantly access past versions of your data to audit, troubleshoot, or analyze trends without downtime or complex recovery steps.

Real Life Example

A finance team needs to verify the numbers reported last quarter. Instead of restoring old databases, they run a simple query to see the exact data as it was on the report date.

Key Takeaways

Manual data recovery is slow and error-prone.

Snowflake's time travel queries let you see data as it was at any past time.

This makes auditing and troubleshooting quick and reliable.

Practice

(1/5)
1. What does the AT clause do when querying historical data in Snowflake?
easy
A. Shows data exactly at a specified point in time
B. Shows data after a specified point in time
C. Shows data before a specified point in time
D. Shows the latest data ignoring time

Solution

  1. Step 1: Understand the purpose of AT clause

    The AT clause is used to query data as it existed exactly at a specific timestamp.

  2. Step 2: Compare with other time clauses

    Unlike BEFORE, which shows data just before a time, AT shows the exact snapshot at that time.

  3. Final Answer:

    Shows data exactly at a specified point in time -> Option A

  4. Quick Check:

    AT = exact time snapshot [OK]
Hint: Remember: AT means exact time snapshot, not before or after [OK]
Common Mistakes:
  • Confusing AT with BEFORE clause
  • Thinking AT shows data after the time
  • Assuming AT ignores time and shows latest data
2. Which of the following is the correct syntax to query a table named sales as it was exactly at timestamp '2024-01-01 10:00:00' using Snowflake's time travel feature?
easy
A. SELECT * FROM sales AT '2024-01-01 10:00:00';
B. SELECT * FROM sales AT (TIMESTAMP => '2024-01-01 10:00:00'; )
C. SELECT * FROM sales AT (TIMESTAMP => '2024-01-01 10:00:00')
D. SELECT * FROM sales BEFORE (TIMESTAMP => '2024-01-01 10:00:00');

Solution

  1. Step 1: Identify correct syntax for AT clause

    Snowflake requires the AT clause with parentheses and the keyword TIMESTAMP => for time travel queries.

  2. Step 2: Check syntax details

    SELECT * FROM sales AT (TIMESTAMP => '2024-01-01 10:00:00') correctly uses AT (TIMESTAMP => '2024-01-01 10:00:00') without a trailing semicolon inside the query string.

  3. Final Answer:

    SELECT * FROM sales AT (TIMESTAMP => '2024-01-01 10:00:00') -> Option C

  4. Quick Check:

    Correct AT syntax = SELECT * FROM sales AT (TIMESTAMP => '2024-01-01 10:00:00') [OK]
Hint: Use AT (TIMESTAMP => 'timestamp') with parentheses for time travel [OK]
Common Mistakes:
  • Using BEFORE instead of AT for exact time
  • Omitting parentheses around TIMESTAMP clause
  • Adding semicolon inside query string causing syntax error
3. Given the table orders with changes over time, what will the following query return?
SELECT COUNT(*) FROM orders BEFORE (TIMESTAMP => '2024-03-01 12:00:00');
medium
A. Count of rows just before '2024-03-01 12:00:00'
B. Count of rows after '2024-03-01 12:00:00'
C. Count of rows exactly at '2024-03-01 12:00:00'
D. Count of all current rows ignoring time

Solution

  1. Step 1: Understand BEFORE clause behavior

    The BEFORE clause returns data as it existed just before the specified timestamp.

  2. Step 2: Apply to COUNT query

    The query counts rows in orders table as they were immediately before '2024-03-01 12:00:00'.

  3. Final Answer:

    Count of rows just before '2024-03-01 12:00:00' -> Option A

  4. Quick Check:

    BEFORE = data just before time [OK]
Hint: BEFORE means data snapshot just before the timestamp [OK]
Common Mistakes:
  • Confusing BEFORE with AT clause
  • Assuming BEFORE returns data after the timestamp
  • Thinking BEFORE returns current data
4. You wrote this query but got a syntax error:
SELECT * FROM customers AT TIMESTAMP => '2024-05-01 09:00:00';

What is the likely cause?
medium
A. Table name should be in quotes
B. Missing parentheses around the TIMESTAMP clause
C. Timestamp format is incorrect
D. Using BEFORE instead of AT

Solution

  1. Step 1: Check syntax for AT clause

    The AT clause requires parentheses around the TIMESTAMP => '...' part.

  2. Step 2: Identify missing parentheses

    The query misses parentheses, causing a syntax error.

  3. Final Answer:

    Missing parentheses around the TIMESTAMP clause -> Option B

  4. Quick Check:

    AT clause needs parentheses [OK]
Hint: Always wrap TIMESTAMP clause in parentheses after AT [OK]
Common Mistakes:
  • Omitting parentheses around TIMESTAMP
  • Confusing syntax with BEFORE clause
  • Incorrect timestamp format causing error
5. You want to compare the number of rows in the transactions table exactly at '2024-04-15 08:00:00' and just before that time. Which pair of queries correctly achieves this?
hard
A. SELECT COUNT(*) FROM transactions BEFORE (TIMESTAMP => '2024-04-15 08:00:00');
SELECT COUNT(*) FROM transactions AT TIMESTAMP => '2024-04-15 08:00:00');
B. SELECT COUNT(*) FROM transactions BEFORE (TIMESTAMP => '2024-04-15 08:00:00');
SELECT COUNT(*) FROM transactions AFTER (TIMESTAMP => '2024-04-15 08:00:00');
C. SELECT COUNT(*) FROM transactions AT (TIMESTAMP => '2024-04-15 08:00:00');
SELECT COUNT(*) FROM transactions AT (TIMESTAMP => '2024-04-15 07:59:59');
D. SELECT COUNT(*) FROM transactions AT (TIMESTAMP => '2024-04-15 08:00:00');
SELECT COUNT(*) FROM transactions BEFORE (TIMESTAMP => '2024-04-15 08:00:00');

Solution

  1. Step 1: Identify query for exact time

    Use AT (TIMESTAMP => '2024-04-15 08:00:00') to get data exactly at that timestamp.

  2. Step 2: Identify query for just before time

    Use BEFORE (TIMESTAMP => '2024-04-15 08:00:00') to get data just before that timestamp.

  3. Step 3: Verify option matches both queries

    SELECT COUNT(*) FROM transactions AT (TIMESTAMP => '2024-04-15 08:00:00');
    SELECT COUNT(*) FROM transactions BEFORE (TIMESTAMP => '2024-04-15 08:00:00'); correctly uses AT and BEFORE clauses as required.

  4. Final Answer:

    SELECT COUNT(*) FROM transactions AT (TIMESTAMP => '2024-04-15 08:00:00');
    SELECT COUNT(*) FROM transactions BEFORE (TIMESTAMP => '2024-04-15 08:00:00');     -> Option D

  5. Quick Check:

    AT = exact, BEFORE = just before [OK]
Hint: Use AT for exact time, BEFORE for just before time [OK]
Common Mistakes:
  • Swapping AT and BEFORE clauses
  • Using AFTER which is invalid in Snowflake time travel
  • Using two AT queries with different timestamps
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard