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.
· SQL Server 2005 database resources depend upon physical disk resources, which store data, and SQL network name resource. If you use mount points together with physical disks, every mount point must seem as cluster resource. Furthermore, every mount point needs to be added as SQL Server dependency. If you add only the dependency of root physical and do not add mount points, MS SQL Server Database (MDF) corruption takes place on failover. Database corruption can also occur if you reboot SQL Server without failing over.
If you add any resources to SQL Server group, they must always have unique SQL network name and SQL IP address. Do not employ existing SQL IP address and SQL network name for anything, expecting SQL Server. If you share the SQL resources with other database resources, you may encounter the below issues:
· Unexpected outages.
· Service pack installations may not be completed successfully.
· SQL Setup program may not complete successfully. Further, you will not be able to install extra instances of MS SQL Server or do routine maintenance.
In such circumstances of database corruption, you need to perform MDF Repair by restoring the damaged database from the most recent backup.
If the backup is not available or its not updated, third-party MDF Database Recovery software are required to repair and restore the database. The MDF Repair applications are capable of restoring all of the database objects in all cases of corruption.
Stellar Phoenix SQL Recovery is an easy and safe to use utility that effectively handles all MDF corruption scenarios. The software restores tables, reports, forms, stored procedures, and triggers. It works well with Microsoft SQL Server 2008, 2005, and 2000.