As you may know, I've been teaching the SQL Server portion of the SharePoint MCM since it started. The old database maintenance whitepaper for SharePoint 2007 had all kinds of things wrong with it and the publishing of the updated whitepaper for SharePoint 2010 was eagerly awaited by the community. Unfortunately it too had a bunch of problems so I offered to get involved and comprehensively review and rewrite it, and did so just before the summer.
It's finally been republished with all my revisions and you can download it from: http://technet.microsoft.com/en-us/library/cc262731.aspx
Enjoy!
7 thoughts on “SharePoint 2010 database maintenance whitepaper”
Thank you for your great job.
Thanks for sharing this. I can’t wait to go over this with our sysadmins who currently manage our SharePoint databases.
Great Paper. I just have one questions. In our shop we separate the MOSS/Sharepoint admins from the DBA’s. On the DBA side we run index maintenance, Checkdb, backups, etc on a regular basis ( index maint, backups daily) and CheckDB weekly. If I read the paper correctly, it looks like Sharepoint\Moss has its’ own timer jobs that also do the index maintenance. It seems like we might be doing it too often. It is your experience that the index maintenance is done by one group or the other? Can the timer job be easily identified and turned off?
I apologize if this is the wrong place to ask these questions.If there is a better place please let me know
Thanks Paul! I’m very relieved that this debacle got sorted out!
-Michael
PS: Yes, the timer jobs can be turned off. My opinion is that if there is a DBA managing the SQL Servers, disable the database maintenance timer jobs. They are really meant for systems without a fulltime DBA who understands the system and its usage patterns.
SharePoint-specific questions are best asked on the MSDN SharePoint forums – I’m not a SharePoint expert. See http://social.msdn.microsoft.com/forums/en-US/category/sharepoint/
Hi Paul, What’s your opinion on having autostats and createstats set for SharePoint 2010 databases? From a DBA perspective I’d normally suggest that these are always set – however I believe there are SharePoint recommendations out there that suggest turning them off for particular databases (I assume to maintain consistant query plans?).
You need to go with the SharePoint recommendations.