You administer a Microsoft SQL Server 2016 server that hosts a transactional database and a reporting database.
The transactional database is updated through a web application and is operational throughout the day.
The reporting database is only updated from the transactional database.
The recovery model and backup schedule are configured as shown in the following table:
At 16:20 hours, you discover that pages 17, 137, and 205 on one of the database files are corrupted on the transactional database. You need to ensure that the transactional database is restored. You also need to ensure that data loss is minimal.
What should you do?
A . Perform a partial restore.
B . Restore the latest full backup, and restore the latest differential backup. Then, restore each log backup taken before the time of failure from the most recent differential backup.
C . Perform a point-in-time restore.
D . Restore the latest full backup.
E . Restore the latest full backup, and restore the latest differential backup. Then, restore the latest log backup.
F . Perform a page restore.
G . Restore the latest full backup. Then, restore each differential backup taken before the time of failure from the most recent full backup.
H . Restore the latest full backup. Then, restore the latest differential backup.
Answer: F
Explanation:
The goal of a page restore is to restore one or more damaged pages without restoring the whole database. Typically, pages that are candidates for restore have been marked as "suspect" because of an error that is encountered when accessing the page.
Note: Requirements for Restoring Pages
A page restore is subject to the following requirements:
– The databases must be using the full or bulk-logged recovery model. Etc.
References: https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-pages-sqlserver