Fixing “Incorrect PFS free space information...” Error Message

An MS SQL Server database file is divided into various PFS (Page Free Space) intervals, approximately 64 MB in size. The byte-map of the PFS page consists of at least one byte per page for every page that is included in the PFS interval. The information stored in the PFS interval is very critical because corruption of it can result into database error, which stops you from accessing the records stored in the database. In such situations, the database corruption can be surmounted by restoring the data from an updated backup. However, the possibilities of database users forgetting to create an adequate backup, or the location where the backup is saved always exits. In such cases, the database user needs to opt for a powerful third-party SQL Database Recovery utility that can easily repair the database.

Picture a scenario, where you receive the underneath error message with your MS SQL Server database:

“Incorrect PFS free space information for page P_ID, object ID O_ID, index ID I_ID, in database ID DB_ID. Expected value PFS_VAL1, actual value PFS_VAL2.”

The above error is marked as “Error 8914” in SQL Server log and is a “Severity Level 10” error message.

Cause:

The above error message pops up when the bits allocated in the PFS page conflict with the free space available on the page P_ID. This can either occur due to logical or physical damage of the database.

Resolution:

The resolutions for the above error message are discussed below:

To check for hardware damages, check the system's hardware by examining the log reports of SQL Server and Windows. Change the hardware component in case any component is damaged.
If the problem persists, run DBCC CHECKDB command (with repair clause) to repair the corrupt database.

However, there is a possibility of data loss after running the above command. To avoid such situations, you should repair your database using effective SQL Repair software. These SQL Repair tools perform a complete scan and restore the repaired database on new or old destination. Such tools are completely non-destructive in nature.

Check this sql related article :-
http://ezinearticles.com/?Troubleshooting-SQL-Server-Error-2579&id=2857699

http://www.thefreelibrary.com/Applying+CHECKDB+on+Tempdb+Cause+Data+Loss-a01073994023