When cloning a database or schema, tables are cloned, which means the internal stage associated with each table is also cloned but the cloned table stages are empty.

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, tables are cloned, which means the internal stage associated with each table is also cloned but the cloned table stages are empty.

Explanation:
Zero-copy cloning lets you create a separate object that points to the same underlying data, but owns its own metadata. When you clone a database or schema, the tables are cloned along with their associated internal stages. The important detail is that the clone gets its own stage object, but the data inside that stage isn’t copied over. The cloned table’s stage starts empty, so you’d need to stage data into it (PUT into the clone’s stage or COPY INTO from another source) if you want to populate it for the clone. This lets the clone operate independently for new data while still sharing the same underlying table data where appropriate.

Zero-copy cloning lets you create a separate object that points to the same underlying data, but owns its own metadata. When you clone a database or schema, the tables are cloned along with their associated internal stages. The important detail is that the clone gets its own stage object, but the data inside that stage isn’t copied over. The cloned table’s stage starts empty, so you’d need to stage data into it (PUT into the clone’s stage or COPY INTO from another source) if you want to populate it for the clone. This lets the clone operate independently for new data while still sharing the same underlying table data where appropriate.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy