Historical data available to query in a primary database using Time Travel is not replicated to secondary databases.

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

Multiple Choice

Historical data available to query in a primary database using Time Travel is not replicated to secondary databases.

Explanation:
Time Travel lets you query data as it existed at a past point within the database. That historical data is tied to the primary account’s storage and retention. When you replicate a database to a secondary account, only the current state of objects and data is brought over; the historical versions used for Time Travel aren’t replicated across accounts. The secondary gets its own Time Travel window, independent of the primary. So the historical data available on the primary through Time Travel isn’t automatically available on the secondary. If you need time-travel access on the secondary, you’d rely on that account’s own Time Travel window or other recovery methods.

Time Travel lets you query data as it existed at a past point within the database. That historical data is tied to the primary account’s storage and retention. When you replicate a database to a secondary account, only the current state of objects and data is brought over; the historical versions used for Time Travel aren’t replicated across accounts. The secondary gets its own Time Travel window, independent of the primary. So the historical data available on the primary through Time Travel isn’t automatically available on the secondary. If you need time-travel access on the secondary, you’d rely on that account’s own Time Travel window or other recovery methods.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy