Time Travel can be disabled for individual databases, schemas, and tables by setting DATA_RETENTION_TIME_IN_DAYS to 0.

• A. True
• B. False
• C. Not possible
• D. Only for Accounts

Answer: (A)

Time Travel retention is configurable at the level of each object, and a value of zero truly disables Time Travel for that object. You can set DATA_RETENTION_TIME_IN_DAYS to 0 on a database, on a schema within a database, or on an individual table, effectively removing the ability to query past states for that specific object. For example, you can run ALTER DATABASE mydb SET DATA_RETENTION_TIME_IN_DAYS = 0; or ALTER SCHEMA mydb.myschema SET DATA_RETENTION_TIME_IN_DAYS = 0; or ALTER TABLE mydb.myschema.mytable SET DATA_RETENTION_TIME_IN_DAYS = 0;. If Time Travel is disabled, you still rely on Fail-Safe for data recovery after deletion, which is a separate mechanism. To re-enable Time Travel, set a positive number again. This is why the statement is true.