Streamling the SharePoint Update Process to Reduce Downtime

Written By: Wahid Saleemi -- 2/9/2011 -- join -- contribute -- (3319) comments -- printer friendly version

Rating: Rate --

Categories: MOSS 2007, SharePoint 2010, SharePoint Foundation 2010, System Administration, WSS3

< Prev - 1 | 2 | 3 | - Next > | Become a paid author


Microsoft has improved the quality and frequency of updates for SharePoint since MOSS 2007 was released by using cumulative updates. However, as a SharePoint Administrator, you'll have to deal with downtime while these updates install. Some updates may even require reboots, disconnecting from the farm and running PSConfig (also known as the SharePoint Products and Technologies Wizard). Because some updates make changes at the database level, having very large databases will potentially cause hours of downtime for the entire farm.


Luckily, we have a trick that can be used to apply updates more quickly and isolate large content databases so they aren't holding up everyone else. This procedure involves detaching any large content databases, applying the updates, and then re-attaching the content databases. Since the databases will not be visible to SharePoint, no updates will be applied to them until they are re-attached. Let's look at a few ways to do this.

< Prev - 1 | 2 | 3 | - Next >

Learn more about SharePoint

Sponsor Information

Copyright (c) 2010-2017 Edgewood Solutions, LLC All rights reserved
privacy | disclaimer | copyright | advertise | contribute | feedback | about
Some names and products listed are the registered trademarks of their respective owners. |