When cloning a database or schema, which pipes are cloned?

Master the SnowPro Advanced Architect Test with flashcards, multiple-choice questions, and detailed explanations. Prepare thoroughly for your certification!

Multiple Choice

When cloning a database or schema, which pipes are cloned?

Explanation:
When you clone a database or schema, Snowflake copies metadata rather than duplicating the actual data. Pipes are part of that metadata, and how they are carried over depends on what they reference. If a pipe uses an external stage (a location outside Snowflake, like S3 or Azure Blob), the clone preserves that pipe and its reference to the external stage, so ingestion can continue from the same external location in the cloned object. Internal stages, however, are bound to the database itself, and their definitions aren’t carried over automatically in a clone, so pipes that point to internal stages aren’t cloned in the same way. That’s why pipes that reference external stages are cloned. If you need a pipe in the clone that uses an internal stage, you’d typically recreate or adjust it to align with the clone’s structure.

When you clone a database or schema, Snowflake copies metadata rather than duplicating the actual data. Pipes are part of that metadata, and how they are carried over depends on what they reference. If a pipe uses an external stage (a location outside Snowflake, like S3 or Azure Blob), the clone preserves that pipe and its reference to the external stage, so ingestion can continue from the same external location in the cloned object. Internal stages, however, are bound to the database itself, and their definitions aren’t carried over automatically in a clone, so pipes that point to internal stages aren’t cloned in the same way. That’s why pipes that reference external stages are cloned. If you need a pipe in the clone that uses an internal stage, you’d typically recreate or adjust it to align with the clone’s structure.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy