File Header and Boot Page Corrupted in MS SQL Server Database

Just like any other database, MS SQL Server database contains a file header page and boot page. While the file header page (8KB) consists of metadata information about the database, the boot page contains critical information about the database itself. Corruption in any of the above pages primarily results in an error message that result in unmounting of the SQL database. This further results in the inaccessibility of SQL database records, used for various personal and professional uses. In such cases, an ideal way to resolve the above error message is by restoring data from an updated backup. But with inaccessibility of database backup, the only option to access your records is by using an advanced SQL Recovery  application.

Consider a practical case, where either of the below error messages pops up when you attempt to access your SQL Server database:

“Msg 5172, Level 16, State 15, Line 1
The header for file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\FileHeaderTest.mdf' is not a valid database file header. The PageAudit property is incorrect.”
Or
“Msg 913, Level 16, State 4, Line 1
Could not find database ID 19. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.”

The first error message is caused due to corruption of file header page and the second is a result of boot page corruption. The database records become inaccessible after any of the above error message pops up.

Read more: .NET Journal

Posted via email from jasper22's posterous