I have found this article on American chronicle. This article may helpful to you to recover and repair damaged mdf file. You can see the full article by the visiting this link
http://www.americanchronicle.com/articles/view/177453. If you have still problem regarding mdf file corruption then have a look on this
repair mdf file software. This software may help you more.
A page is the most primitive unit of storage in an MS SQL Server database. The memory space allotted to a database file is divided into pages having contiguous address location. An Index Allocation Map (IAM) is a page type that stores the details about the extents used by a table per allocation unit. However, sometimes these pages do not function properly because of database corruption. You should take appropriate corrective measures to recover SQL database. However, if you are not able to restore the database then you should use a third-party
mdf recovery software to do the needful for you.
Consider a scenario wherein you encounter the following error message while working on an SQL Server 2008 database table:
“An inconsistency was detected during an internal operation in database '%.*ls'(ID:%d) on page %S_PGID. Please contact technical support. Reference number %ld.”
Cause:...
You may come across SQL Server database corruption if the registry checkpoint of SQL Server agent is missing. In this case, SQL Server Agent cannot be found and MS SQL Server cannot start up. In such situations, MDF (Master Database File) of SQL Server becomes inaccessible and you come across critical data loss situations. To work around this problem,
MDF Database Recovery is essential, if you do not have an updated backup.
As a practical example of this problem, consider this scenario:
The Registry checkpoint of SQL Server Agent is missing due to some unexpected deletion or unexpected corruption problems in the clustered instance of MS SQL Server 2008.
Clustered instance of Microsoft SQL Server 2008 is repaired.
In the above scenario, you cannot find the registry subkey, which is associated with the SQL Server Agent, in list of the checkpoints of SQL Server Network Name resource. SQL Server Network Name is associated with clustered instance. Furthermore, updates of SQL Server Agent application configuration aren't spread to other cluster nodes when SQL Server resource group goes to the nodes...
A particular set of resources, which have dependencies on several other resources is created, when you set up MS SQL Server on any cluster. You should not ever alter the default resources dependency tree. It may lead to several consistency and integrity issues in Microsoft SQL Server database. It may also lead to serious database corruption problems and need
MDF Recovery to work around the issue.
Microsoft SQL Server Agent and Microsoft SQL Server shouldn't depend on a resource, other than specified resources. You are recommended not to make other database resources dependent upon MS SQL Server Agent or MS SQL Server. If it is essential to have dependency, you must play safely and follow the guidelines, recommended by Microsoft.
The default resource dependency tree of MS SQL Server has the below implications:
The MS SQL Server Agent resources depend upon SQL Server resources...
