Help, my database is corrupt. Now what?

A corrupt database is probably one of most DBA's worst nightmares. It results in downtime, managers shouting and all other sorts of unpleasant things

In this article, I'm going to explain some of the things not to do to a corrupt database, and then go through some of the things that should be done, some of the scenarios and the fixes for those.

HYPER-V CERTIFICATE EXPIRATION AND RESOLUTION

For those of you who’ve enabled the Hyper-V role in WS08. It has been determined that a certificate error can occur resulting in the inability to start or connect to virtual machines running on Windows Server 2008 or Microsoft Hyper-V Server 2008.  The Hyper-V virtualization host and the existing virtual machines will continue to operate without disruption.  A hotfix designed to prevent/resolve this error has been created and is available for download starting today.  The following is a brief description of the issue as well as a link to the KB Article that provides the resolution.  Even if you are not currently experiencing this issue, we recommend you download and install this update.

 

THIS APPLIES TO THE FOLLOWING:

• Windows Server 2008, Standard (Hyper-V role enabled)
  
• Windows Server 2008, Enterprise (Hyper-V role enabled)
  
• Windows Server 2008, Datacenter (Hyper-V role enabled)
  
• Microsoft Hyper-V Server 2008
  

 

SYMPTOMS AND RESOLUTION:

• You may be unable to start or connect to virtual machines running on Windows Server 2008 or Microsoft Hyper-V Server 2008. This occurs when connecting using vmconnect. Connections made using remote desktop won't be affected.  
  
• KB Article 967902 has been created that details the symptoms and resolution.  This KB article provides a direct link to download the quickfix to resolve this error.
  

http://blogs.technet.com/windowsserver/archive/2009/03/02/Hyper_2D00_V-certificate-expiration-and-resolution.aspx