| A database page is the most primitive storage unit in | | | | Resolution: |
| an SQL Server database. These pages are stored | | | | You should perform the following methods to repair |
| sequentially in the hard disk. When any operation is | | | | SQL database in the given order: |
| performed on the database, these page act as the | | | | Check for hardware issues: You should run the |
| basic I/O unit. Every page contains a file header, of 96 | | | | hardware diagnostics and check the event logs to |
| bytes, that contains page information such as page | | | | determine whether there is any hardware |
| type, page number, object ID, etc. Sometimes these | | | | malfunctioning. You can also swap the hardware |
| pages do get corrupt because of various reasons | | | | components to isolate the cause of error. As a last |
| such as virus infections, power outages, hardware | | | | resort, you can also consider reformatting the hard |
| malfunctioning, etc. You should resolve the situation by | | | | disks and reinstalling the operating system. However, |
| taking appropriate corrective measures. If you are not | | | | before doing this you should backup your important |
| able to provide any solution, then you should use a | | | | data. |
| third-party mdf repair software to recover the data. | | | | Restore from backup: If the issue is not because of |
| Consider a scenario wherein you encounter the | | | | faulty hardware then you should check for the backup |
| following error message while working on an SQL | | | | of the database. If the backup is clean and updated, |
| Server 2008 database: | | | | then you should restore the database from the |
| “Database error: PAGE_TYPE page P_ID for | | | | backup. |
| database 'NAME' (database ID DB_ID) is invalid. This | | | | The aforementioned methods will be able to address |
| error cannot be repaired. You must restore from | | | | the problem. However, if the problem is still there or the |
| backup.” | | | | backup is not updated then you should use a |
| Cause: | | | | third-party SQL repair software to repair SQL |
| The root cause of this error is that either the file | | | | database. Such tools are read-only in nature that do |
| header page or the boot page in the database is | | | | not overwrite the existing data while scanning the |
| corrupted. This situation is identified as Event ID 5250 in | | | | system. |
| SQL Server 2008. | | | | |