0% found this document useful (0 votes)
115 views10 pages

13.TimeTravel and FailSafe

Uploaded by

clouditlab9
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
115 views10 pages

13.TimeTravel and FailSafe

Uploaded by

clouditlab9
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Time Travel and Fail-safe

by
Janardhan
Bandi
Agenda
• Time Travel
• Retention Period
• Querying historical data
• Restoring Objects
• Fail Safe
• Continuous Data Protection Life Cycle
Time Travel
• Snowflake Time Travel enables accessing historical data (i.e. data that has been
changed or deleted) at any point within a defined period.
• Restoring data-related objects (tables, schemas, and databases) that might have
been accidentally or intentionally deleted.
• Query data in the past that has since been updated or deleted.
• Duplicating and backing up data from key points in the past.
• Analyzing data usage/manipulation over specified periods of time.
• No need to enable Time Travel, it is automatically enabled.
Retention Period
• Retention is the key component of Time Travel.
• It specifies the number of days for which this historical data is preserved.
• For Standard Edition, the retention period is 1 day, can set it to 0.
• For Enterprise and higher editions it is 90 days, can set it any thing between 0-90
days.
• Default is 1, we can set this period at the time of creation of object or can alter later.
• A retention period of 0 days for any object means disabling Time Travel for the
object.
• We can change the retention period by using ALTER command.
• Higher retention period, the higher storage cost.
Querying Historical Data
3 Ways to query historical data
1. At specified timestamp
2. At some time ago
3. Before executing any statement/query
Querying Historical Data
1. Below query selects historical data from a table at the specified timestamp:
select * from my_table at(timestamp => 'Fri, 01 May 2015 16:20:00 -0700'::timestamp_tz);

2. Below query selects historical data from a table as of 5 minutes ago:


select * from my_table at(offset => -60*5);

3. Below query selects historical data that present in the table before executing the
query specified by query id
select * from my_table before(statement => '8e5d0ca9-005e-44e6-b858-a8f5b37c5726');
Restoring Objects
• When a table, schema, or database is dropped, it is not immediately removed
from the system.
• Instead, it is retained for the data retention period for the object, during which
time the object can be restored.
• After retention period is completed, we can’t restore the objects.

UNDROP TABLE ‘TABLE_NAME’


UNDROP SCHEMA ‘SCHEMA_NAME’
UNDROP DATABASE ‘DATABASE_NAME’
Fail-safe
• Fail-safe provides a 7-day period during which historical data may be recoverable
by Snowflake.
• This period starts immediately after the Time Travel retention period ends.
• We can't query or restore the Fail-safe data.
• We need to contact Snowflake Support to restore the data during Fail-safe period.
• Data recovery through Fail-safe may take several hours to several days to
complete.
• After Fail-safe period is over, there is no other way to recover the data.
Continuous Data Protection Life
Cycle
Thank You

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy