[SQL Server] Perform page recovery
BLOG
7/1/20241 min lire
SQL Server databases newly created use checksum page verification, by default. If a page's checksum is invalid that means that the page has been corrupted. The database engine keeps track of page corruptions in the msdb system database's suspect_pages table.
If your database only has a small number of isolated pages that are damaged, you can take advantage of the page restore process. It is quicker to restore a small number of pages than to restore an entire database.
Page restore only works for read/write files in databases that are using the full or bulk-logged recovery models. Page restore cannot be used for corruption in the transaction log.
Page restore does not work for the following types of database pages :
Database Boot Page (Page 1:9)
File Boot Page (Page 0 of all data files)
Full-text catalog
Global Allocation Map (GAM)
Page Free Space (PFS)
Secondary Global Allocation Map (SGAM)
Page restore works with all editions of SQL Server. Only SQL Server Enterprise Edition supports online page restore.
see also : [SQL Server] Restore a filegroup