A stream called TRANSACTIONS_STM is created on top of a TRANSACTIONS table in a continuous pipeline running in Snowflake. After a couple of months, the TRANSACTIONS table is renamed TRANSACTIONS_RAW…

Question

Options

• ATRANSACTIONS_STM will keep working as expected.
• BTRANSACTIONS_STM will be stale and will need to be re-created.
• CTRANSACTIONS_STM will be automatically renamed TRANSACTIONS_RAW_STM.
• DReading from the TRANSACTIONS_STM stream will succeed for some time after the expected

• A
  89% (24)
• B
  7% (2)
• D
  4% (1)

Explanation

In Snowflake, streams are linked to their source table via an internal object ID, not the table's name - so renaming the table does not break the stream; TRANSACTIONS_STM continues tracking changes on the same underlying object without interruption. Option B is wrong because the stream's metadata is ID-based, not name-based, so no staleness or re-creation is needed. Option C is wrong because Snowflake does not auto-rename dependent objects when a table is renamed - that would require explicit DDL. Option D is wrong because access doesn't degrade over time; the stream either works or it doesn't, and in this case it keeps working indefinitely.

Memory tip: Think of Snowflake objects as having a "social security number" (object ID) separate from their "name" - a stream holds the SSN, not the name tag, so renaming doesn't confuse it.

No community discussion yet for this question.