Corruption in database (.MDF\/.NDF) files can result in the “Incorrect PFS free space information” error. Corruption in database files can occur due to the reasons mentioned below:<\/p>
- \n
- Sudden system shutdown<\/li>\n\n\n\n
- Bugs in MS SQL Server<\/li>\n\n\n\n
- Large or oversized database file<\/li>\n\n\n\n
- MS SQL Server shuts down incorrectly or unexpectedly when the database is open<\/li>\n\n\n\n
- Issue with the hard disk where database is saved<\/li>\n\n\n\n
- System on which the data files are saved is virus-infected<\/li>\n<\/ul>
Methods to Fix Incorrect PFS Free Space Information Error<\/strong><\/h2>
The “Incorrect PFS free space information” error appears when the DBCC CHECKDB command<\/a> detects corruption in the database. It displays the object name, table name, object ID, Partition ID, and Page ID, and recommends an appropriate repair option. So, you can move the data to new pages, restore the database from backup, or repair the database to try to resolve the error. Here’s how.<\/p>
1 – Move Data to New Pages<\/strong><\/h3>
The DBCC CHECKDB command displays the table name in which problematic PFS pages are located. You can try to copy the data from source table to a new table. This will assign new data pages and PFS entries. After this, delete the source table and rename the new table same as the source table. This can help in troubleshooting the error.<\/p>
Note:<\/em><\/strong> This will work if you know the table name to which the problematic PFS pages belong.<\/em><\/p>
2 – Restore the Database from Backup<\/strong><\/h3>
If the database is corrupted, damaged, or unreadable, you can restore the database from the last updated backup. You can use the SQL Server Management Studio (SSMS) to restore the SQL database backup. Follow the steps mentioned below:<\/p>
- \n
- Open the SSMS and go to the Object Explorer.<\/strong><\/li>\n\n\n\n
- Right-click Databases <\/strong>and select the Restore Database<\/strong> option.<\/li>\n<\/ul>
![\"go](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2024\/07\/go-to-databases-click-restore-database.png\")
<\/figure>- \n
- On the General <\/strong>page, under the Source <\/strong>section, select Device<\/strong> to specify the source and location of the backup sets to restore.<\/li>\n<\/ul>
![\"click](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2024\/07\/click-device-under-general-option.png\")
<\/figure>- \n
- In the Destination<\/strong> section, select the database name.<\/li>\n\n\n\n
- In the Restore to <\/strong>field, you can leave the default as To the last backup taken<\/strong>.<\/li>\n\n\n\n
- In the Backup sets to restore<\/strong> grid, click on the backups you need to restore.<\/li>\n\n\n\n
- On the Options<\/strong> page, under Restore options<\/strong> section, you can select the required options. Then, click OK.<\/strong><\/li>\n<\/ul>
![\"click](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2024\/07\/click-options-under-restore-options-select-required-options.png\")
<\/figure>Alternatively, you can restore the database from backup by running the following T-SQL code:<\/p>
RESTORE DATABASE [employee] FROM DISK = N'C:\\Backup\\employee.bak' WITH FILE = 1, NOUNLOAD, STATS = 10<\/code><\/p>Here, ‘employee’ is the database name and ‘N’C:\\Backup\\employee.bak’ is the location where the backup is stored. The file is FILE 1 and STAT = 10 will display restoration progress every 10%.<\/p>
3 – Repair Database using the DBCC CHECKDB Command<\/strong><\/h3>
If you don’t have an updated backup, then you can use the DBCC CHECKDB<\/a> command to repair the database. It can repair all the objects in corrupt SQL database, including index pages, PFS pages, and other allocation pages. You can run the DBCC CHECKDB<\/strong> command with the REPAIR_ALLOW_DATA_LOSS<\/strong> option as given below:<\/p>
Note:<\/strong> Before using the command, it is suggested to take the backup of your SQL database.<\/p>
DBCC CHECKDB ('employee', REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS;<\/code><\/p>GO<\/code><\/p>Note:<\/em><\/strong> Repairing SQL database with DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS command reallocate the PFS pages or series of pages. It can cause data loss. <\/em><\/strong><\/p>
In case the DBCC CHECKDB command fails, then you can use a reliable third-party S<\/a>QL repair tool<\/a>, such as Stellar Repair for MS SQL. This tool can easily repair SQL database files (.mdf and .ndf) without any data loss. It can recover all the objects from the corrupt database, including pages, indexes, tables, and stored procedures. It then saves the recovered data to a new healthy database file (.mdf). This helps in resolving the issues occurred due to corruption in the database file. The tool supports repair and recovery of databases created in SQL Server 2022, 2019, 2017, 2016, and older versions.<\/p>
Conclusion<\/strong><\/h2>
The “Incorrect PFS free space information” error occurs when the SQL search engine fails to read the PFS pages. If the page free space pages in database files are corrupted, you can restore the database from the last backup. However, if the backup is not updated, then you can repair the database using the DBCC CHECKDB command. However, the best option to repair database without any data loss is by using an advanced SQL database repair tool, like Stellar Repair for MS SQL<\/a>. It is an MVP-recommended tool that can repair both MDF and NDF files. It can recover all the data from the corrupt database file with complete precision.<\/p>\n","protected":false},"excerpt":{"rendered":"
- In the Restore to <\/strong>field, you can leave the default as To the last backup taken<\/strong>.<\/li>\n\n\n\n
- In the Destination<\/strong> section, select the database name.<\/li>\n\n\n\n
- Right-click Databases <\/strong>and select the Restore Database<\/strong> option.<\/li>\n<\/ul>
- Open the SSMS and go to the Object Explorer.<\/strong><\/li>\n\n\n\n