Querying tables and views in a secondary database using Time Travel can yield different results than querying the same objects in the primary database.

• A. True
• B. False
• C. Not applicable
• D. Not known

Answer: (A)

Time Travel shows the state of data as it exists in that specific database at a chosen point in time. When you’re querying a secondary database that was created by replication, you’re looking at a separate copy that is kept in sync with the primary through asynchronous replication. Because replication can lag, the data present on the secondary at a given moment may not reflect the exact same state as the primary at the same moment. As a result, an as-of query against the secondary can produce different results from the primary for the same table or view. In short, the secondary’s data state can be behind the primary, and Time Travel on each database views its own local state.