If there are numerous factors which can damage the SQL server database then there are also numerous methods for MS SQL recovery. Each SQL MDF recovery method is having its own advantages and limitations. Let’s find out that which one out of them can actually solve your purpose.

The FC (Failover Clustering) method for MS SQL recovery

It is a process of evolving clusters when there is a hardware or software failure. With the help of this mechanism a person can generate clusters for single or multiple instances. FC is a good solution for recovering lost files lost because of system or hard disk failure. The NT 4.0, 2000 Advanced Server, Windows 2000 Datacenter Server Windows Server 2003, Enterprise Edition, Windows Server 2003 and Datacenter Edition are some platforms which support the Failover Clustering.

Why Failover clustering method is not preferred to Repair SQL 2000?

This method is quite a lot expensive as compared to the other methods and it works with only on those servers which are in straight line. It cannot restore the data lost because of disk array failure. One more drawback of Failover clustering is that it cannot create clusters at database object level.

MS SQL recovery with DM (Database Mirroring)

It is a best suited method for full recovery model databases. This process is not available for simple database models.

Why Database Mirroring is not preferred for SQL MDF recovery?

DM recovers only those databases which have been interlinked with the principal database. The Technical Managers refuse to use Database Mirroring because of the security concerns during content exchange.

The Peer-to-peer transactional replication method

It is a good MS SQL recovery option for those applications which can read and edit the data in any database. It is a good fit for the databases which are not depending upon the server hosting.

Peer-to-peer transactional replication cannot repair SQL 2000

This method is restrained only to SQL Server 2005 Enterprise Edition. The databases which need to be recovered with transactional replication method should have common schemas. Moreover conflict detection or resolution is not possible with this method.

Maintenance through warm standby server

The MS SQL recovery with maintenance through warm standby server method can be divided into two methods Log shipping and transactional replication.
Log shipping is the method for Microsoft SQL Server 7.0, Microsoft SQL Server 2000 Enterprise Edition and Microsoft SQL Server 2000 Developer Edition.
Transactional replication is the replication of data from server (the publisher) to other server with less latency.

Drawbacks of Log shipping and transactional replication method

If not properly used, then Log shipping can totally affect the functioning of the database. Moreover, it is not possible to restore the table changes for automatic failover of applications.
Many users prefer the Restore Transaction method besides Open Database Connectivity (ODBC) connection in transactional replication method.

RAID (Redundant Array of Independent Disks)
RAID is a mechanism which stores the damaged data on multiple disks.

Limitations

Using RAID is very difficult and it cannot restore the data lost because of multiple disk failures.
One single mechanism which can easily execute MS SQL recovery is Kernel for SQL Recovery. This tool heals the damages and quickly performs the SQL MDF recovery. It can repair SQL 2000, SQL 2005, SQL 2008 and SQL 2008 R2 versions.

View all Austin Paul's articles

---

About the Author:
The Author is having a rich experience of critically analyzing the software’s. He has analyzed various methods for MS SQL recovery. He has mentioned about a SQL MDF recovery tool which can repair SQL 2000, SQL 2005, SQL 2008 and SQL 2008 R2 versions.

More Computers & Internet articles