Data lineage tracking in Snowflake - Commands & Configuration

Introduction

Data lineage tracking helps you see where your data comes from and how it changes. It solves the problem of understanding data flow and impact in your Snowflake environment.

When you want to find the source of a data error in your reports

When you need to understand how data moves between tables and views

When you want to check which processes update a specific dataset

When you need to comply with data governance rules by showing data origins

When you want to optimize your data pipelines by knowing dependencies

Commands

This command sets the current database context to MY_DATABASE so that subsequent commands run in this database.

Terminal

USE DATABASE MY_DATABASE;

Expected Output

Database changed.

This command queries the data lineage for the table MY_SCHEMA.MY_TABLE, showing where its data comes from and what depends on it.

Terminal

SELECT * FROM TABLE(INFORMATION_SCHEMA.LINEAGE_BY_OBJECT('MY_SCHEMA.MY_TABLE'));

Expected Output

OBJECT_NAME          | OBJECT_TYPE | DEPENDENCY_TYPE | DEPENDENT_OBJECT

MY_SCHEMA.MY_TABLE   | TABLE       | BASE            | 

MY_SCHEMA.SOURCE_VIEW| VIEW        | DEPENDENT       | MY_SCHEMA.MY_TABLE

This command shows the lineage of data involved in the given query, helping you understand all data sources and transformations used.

Terminal

SELECT * FROM TABLE(INFORMATION_SCHEMA.LINEAGE_BY_QUERY('SELECT * FROM MY_SCHEMA.MY_TABLE'));

Expected Output

QUERY_ID  | OBJECT_NAME          | OBJECT_TYPE | DEPENDENCY_TYPE

123456789 | MY_SCHEMA.MY_TABLE   | TABLE       | BASE

123456789 | MY_SCHEMA.SOURCE_VIEW| VIEW        | DEPENDENT

Key Concept

If you remember nothing else from this pattern, remember: Snowflake's INFORMATION_SCHEMA functions let you trace data origins and dependencies easily.

Common Mistakes

Running lineage queries without setting the correct database context.

The lineage functions will not find the objects if the database is not set, causing errors or empty results.

Always run USE DATABASE command before lineage queries to set the right context.

Using incorrect object names or schema names in lineage functions.

Misspelled or wrong names cause no results or errors because Snowflake cannot find the objects.

Double-check object and schema names before running lineage queries.

Summary

Set the database context with USE DATABASE before running lineage queries.

Use INFORMATION_SCHEMA.LINEAGE_BY_OBJECT to see data sources and dependencies for a table.

Use INFORMATION_SCHEMA.LINEAGE_BY_QUERY to understand data flow for a specific query.

Practice

1. What is the main purpose of data lineage tracking in Snowflake?

easy

A. To increase storage capacity automatically

B. To show where data comes from and how it moves

C. To encrypt data at rest

D. To create user accounts

Solution

1. Step 1: Understand data lineage concept

   Data lineage tracks the origin and flow of data through systems.

2. Step 2: Match with Snowflake purpose

   Snowflake uses lineage to show data source and movement, not storage or encryption.

3. Final Answer:

   To show where data comes from and how it moves -> Option B

4. Quick Check:

   Data lineage = data origin and flow [OK]

Hint: Data lineage means tracking data origin and flow [OK]

Common Mistakes:

• Confusing lineage with storage management
• Thinking lineage is about encryption
• Mixing lineage with user management

2. Which Snowflake command helps you explore data lineage by showing object dependencies?

easy

A. SHOW OBJECT DEPENDENCIES

B. SHOW USERS

C. DESCRIBE TABLE

D. CREATE WAREHOUSE

Solution

1. Step 1: Identify command for lineage

   SHOW OBJECT DEPENDENCIES lists how objects depend on each other, revealing lineage.

2. Step 2: Eliminate unrelated commands

   SHOW USERS lists users, DESCRIBE TABLE shows table structure, CREATE WAREHOUSE creates compute resources.

3. Final Answer:

   SHOW OBJECT DEPENDENCIES -> Option A

4. Quick Check:

   Lineage command = SHOW OBJECT DEPENDENCIES [OK]

Hint: Use SHOW OBJECT DEPENDENCIES to see lineage [OK]

Common Mistakes:

• Using SHOW USERS for lineage
• Confusing DESCRIBE TABLE with lineage
• Thinking CREATE WAREHOUSE shows dependencies

3. Given the following Snowflake query:

SHOW OBJECT DEPENDENCIES LIKE 'SALES_DATA';

What does this query return?

medium

A. List of users who accessed SALES_DATA

B. List of warehouses running SALES_DATA queries

C. List of tables with similar names to SALES_DATA

D. List of objects that depend on or are used by SALES_DATA

Solution

1. Step 1: Understand SHOW OBJECT DEPENDENCIES usage

   This command shows dependencies related to the specified object, here SALES_DATA.

2. Step 2: Interpret LIKE filter

   LIKE 'SALES_DATA' filters to objects named SALES_DATA, showing their dependencies.

3. Final Answer:

   List of objects that depend on or are used by SALES_DATA -> Option D

4. Quick Check:

   SHOW OBJECT DEPENDENCIES LIKE = dependency list [OK]

Hint: SHOW OBJECT DEPENDENCIES lists related objects [OK]

Common Mistakes:

• Thinking it shows user access logs
• Confusing with warehouse usage
• Assuming it lists similar table names

4. You run SHOW OBJECT DEPENDENCIES LIKE 'CUSTOMER_ORDERS'; but get no results. What is a likely reason?

medium

A. The object name is misspelled or does not exist

B. You need to create a warehouse first

C. SHOW OBJECT DEPENDENCIES does not work on tables

D. Your user lacks SELECT permission on CUSTOMER_ORDERS

Solution

1. Step 1: Check object existence

   No results usually mean the object name is wrong or missing in the database.

2. Step 2: Verify command applicability and permissions

   SHOW OBJECT DEPENDENCIES works on tables; warehouse creation is unrelated; lack of SELECT permission does not hide dependencies.

3. Final Answer:

   The object name is misspelled or does not exist -> Option A

4. Quick Check:

   No results = wrong or missing object name [OK]

Hint: Check spelling and existence if no dependencies show [OK]

Common Mistakes:

• Assuming warehouse needed for lineage
• Thinking permissions block SHOW OBJECT DEPENDENCIES
• Believing tables can't have dependencies

5. You want to track data lineage for a complex pipeline involving multiple views and tables in Snowflake. Which approach best ensures accurate lineage tracking?

hard

A. Only track lineage for base tables, ignoring views

B. Manually document dependencies in a spreadsheet

C. Use SHOW OBJECT DEPENDENCIES and automate lineage extraction with Snowflake metadata queries

D. Rely on user memory to recall data flow

Solution

1. Step 1: Understand lineage complexity

   Complex pipelines need automated, accurate tracking to avoid errors and omissions.

2. Step 2: Evaluate options for accuracy and scalability

   Manual docs and memory are error-prone; ignoring views misses dependencies; using SHOW OBJECT DEPENDENCIES with automation is best practice.

3. Final Answer:

   Use SHOW OBJECT DEPENDENCIES and automate lineage extraction with Snowflake metadata queries -> Option C

4. Quick Check:

   Automate lineage with SHOW OBJECT DEPENDENCIES for accuracy [OK]

Hint: Automate lineage extraction using SHOW OBJECT DEPENDENCIES [OK]

Common Mistakes:

• Relying on manual documentation only
• Ignoring views in lineage tracking
• Trusting memory instead of tools