subject: Sql Server Error - Error Page Game [print this page] MS SQL Server databases are usually classified into various distribution units. That is, for this page (Index Allocation Map), GAM (Global Allocation Map) pages, SGAM (Shared Global Allocation Map) or PFS (Page Free Space) pages. All of these distribution devices must be healthy condition for the successful operation of the SQL database. because of corruption in any of these pages stops the installation of the SQL database, so the lack of databases and other database records, tables, indexes, triggers, views, stored procedures, etc.
MS SQL Server database is generally divided into various allocation units. Namely, IAM (Index Allocation Map) pages, GAM (Global Allocation Map) pages, SGAM (Shared Global Allocation Map), or PFS (Page Free Space) pages. All these allocation units need to be in healthy condition for successful working of SQL database because corruption in any of these pages halts the mounting of SQL database; resulting into inaccessibility of databases and other database records, tables, indexes, triggers, views, stored procedures, etc.
One such similar situation is when GAM allocation page falls prey to corruption, leaving SQL database inaccessible. Following error message occurs: "Page errors on the GAM..."
Error appears whenever you try to mount your MS SQL Server database saying: "Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID DB_ID pages from P_ID1 to P_ID2. See other errors for cause."
The same error message appears repeatedly each time you attempt to mount your database. The above error message is a severity level 16 error message and can be caused either through logical or physical damage.
Various factors can lead to corruption in allocation pages of MDF database. Naming them -unexpected system shutdown, SQL Server damage, virus attacks, software malfunction, human errors, media error, etc. however, corruption in any of GAM, SGAM, or PFS pages of SQL Server Meta structure is the main culprit in this case.
To resolve this corruption issue and to access SQL database records again, try to restore the database from an updated backup. But there are numerous cases, when user forgets to take database backups or to keep them updated. In such situations, use sql recovery software to rescue your SQL database MDF in an efficient manner.
Below series of solutions might prove helpful to you. So follow them.
1) If corruption is caused due to physical damage, then change the damaged system component with a brand new system component.
2) If it's a case of logical damage, run DBCC CHECKDB command, with correct repair clause.
3) In case of failure of above resolutions, restore the data from an updated backup.
One can't be sure that above steps will resolve the problem. So what can be done now? Well use SQL server Database Repair software to repair corrupt SQL server databases in all logical corruption situations. This SQL recovery tool is efficient in its working and performs recursive scan of corrupt MDF files and repairs the damaged primary, foreign and unique keys and creates new SQL server database files. All the database tables, views, stored procedures, user functions and other existing components are recovered completely. Even deleted records, partly damaged records are easily. Software is embedded with powerful repair algorithm that retrieves every bit of data from corrupt MDF databases.
SQL Database Repair tool is easily downloadable for free and can be evaluated for free, no charge. Demo shows the recovered items that can be saved separate script files for rebuilding the database. SQL Recovery software recovers MDF database files created with MS SQL 2000, 2005 and 2008.
Author of this article possess specialization in providing SQL Server tips that include topics like SQL database repair, repair SQL database, MDF file recovery, SQL recovery and many more. His articles enlighten the way to resolve various SQL Server file issues.
