How to Remove Corrupted SharePoint Sites – Preparing for SharePoint 2010 Upgrade
SP2 had a number of enhancements designed around making it easier to upgrade to SharePoint 2010. One such new feature that wasn’t popularized is your ability to find and remove corrupted, broken sites known as orphans. As I’ve mentioned in the past, with SharePoint being split across multiple databases, it is quite possible that a site could be in either the content database OR the config database. With service pack 2 there’s a new way to find orphaned sites. In addition to running STSADM –o PreUpgradeCheck , one of my favorite tools along with TEST-SPContentDatabase with SharePoint 2010 you can identify these messed up corrupted sites. You’ll run enumallwebs (STSADM reference on TechNet) to identify the orphaned sites, and use deletesite (STSADM reference on TechNet) to remove them. Note this command is available in SP2, and was enhanced in the post SP2 October Cumulative update. You really should consider that October update as the most significant release with