DataNumen logo Header Header
  Site Search:
 
  Home » Products » DataNumen SQL Recovery » SQL Server Errors and Problems
 
         
 
Arrow DATANUMEN SQL RECOVERY
   
  News
  Recovery
  Download
  Order
  FAQ
  View Screenshot
  Awards
   
Arrow RELATED PRODUCTS
Arrow DataNumen Access Repair
Arrow DataNumen DBF Repair
Arrow DataNumen Database Recovery
Arrow DataNumen Oracle Recovery
 

Complete List of Errors and Problems in SQL Server MDF Database Files

   

When you use Microsoft SQL Server to attach or access a corrupt MDF database file, you will see various error messages, which may be a bit confusing to you. Therefore, here we will try to list all possible errors, sorted according to their occurring frequency. For each error, we will describe its symptom, explain its precise reason and give sample files as well as the file fixed by our DataNumen SQL Recovery, so that you can understand them better. Below we will use 'xxx.MDF' to express your corrupt SQL Server MDF database file name.

Based on SQL Server or CHECKDB error messages, there are three kinds of errors that will cause failure:

  1. Allocation errors: We know the data in MDF & NDF files are allocated as pages. And there are some special pages that are used for allocation management, as follows:
    Page Type Description
    GAM Page Store global allocation map(GAM) info.
    SGAM Page Store shared global allocation map(SGAM) info.
    IAM Page Store index allocation map(IAM) info.
    PFS Page Store PFS allocation info.

    If any of the above allocation pages have errors, or the data managed by these allocation pages are inconsistent with the allocation information, then SQL Server or CHECKDB will report allocation errors.


  2. Consistency errors: For pages that are used to store data, including the data pages and index pages, if SQL Server or CHECKDB find any inconsistency between the page contents and the checksum, then they will report consistency errors.

  3. All other errors: There may be other errors not fall into the above two categories.
 
 

SQL Server has a built-in tool called DBCC, which has CHECKDB and CHECKTABLE options that can help to repair a corrupt MDF database. However, for severe damaged MDB database files, DBCC CHECKDB and CHECKTABLE will also fail.

 

Consistency errors reported by CHECKDB:

 
 

Allocation errors reported by CHECKDB:

 
 

All other errors reported by CHECKDB: