| PFS (Page Free Space) page in Microsoft SQL | | | | (1:18836), row 34. Test |
| Server database maintains a record of two things - | | | | (ColumnOffsets + (int)sizeof (COLOFF) <= (nextRec |
| allocation of every page and free space available on | | | | - pRec)) failed. Valuesare 31 and 29." |
| each of those pages. The page is the first page and | | | | The above error message appears after the DBCC |
| contains critical information used by SQL Server | | | | CHECKDB command fails to repair the database. |
| engine t the time of allocating pages to any new | | | | Cause: |
| object. While the server can read a PFS page | | | | The above error message appears when the reading |
| anytime, there are a few situations wherein the page | | | | of PFS page fails. This failure occurs when the |
| can not be read. Such situations primarily occur when | | | | database is logically or physically damaged. |
| your database is logically or physically damaged. In | | | | Resolution: |
| most of these corruption scenarios, the database | | | | To repair the database, both in physical and logical |
| becomes unmountable, leading to inaccessibility of | | | | corruption, follow the below mentioned steps: |
| saved records. Additionally, the database administrator | | | | 1.In case of physical damage, change the damaged |
| encounters an error message each time s/he | | | | physical component. |
| encounters the above situation. To overcome the | | | | 2.In case of logical damage, run DBCC CHECKDB with |
| above scenario and to access the database records, | | | | suitable repair clause. However, if logical corruption |
| the user needs to run DBCC CHECKDB command or | | | | persists, then use third-party MS SQL Repair tools to |
| restore the data from an updated backup. However, in | | | | perform complete repair. Such SQL Database Repair |
| case of command failure and no backup available, the | | | | tools use advanced repair techniques to repair any |
| user needs to opt for a commercial SQL Repair | | | | logically damaged database. |
| application. | | | | SQL Recovery Software is the finest repair tool used |
| To elaborate the above case in detail, consider the | | | | by most of the SQL database users to overcome |
| below error message: | | | | DBCC CHECKDB failure. This SQL Database Repair |
| "Server: Msg 8928, Level 16, State 1, Line 1 | | | | utility repairs all the database created in MS SQL |
| Object ID 389576426, index ID 0: Page (1:18836) could | | | | Server 2008, 20005, and 2000. The read-only tool |
| not be processed. Seeother errors for details. | | | | performs safe repair and can be installed on Windows |
| Server: Msg 8944, Level 16, State 1, Line 1 | | | | 7, Vista, 2008, XP, 2003, and 2000. |
| Table error: Object ID 389576426, index ID 0, page | | | | |