Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

So now that I've become the semi-dba at my current job I'm trying to improve a lot of the things that weren't really being considered before. One of these is trying to make sure that databases aren't set to autogrow and are assigned appropriate size limits. My problem is the SharePoint database. Since the databases for SharePoint could grow at unexpected rates I'm not sure what to do with them. I'm looking for some advice from other dbas who manage SharePoint databases.

share|improve this question
1  
Please look at this response from Paul Randel where he briefly touches on my turning off AutoGrow can be a very bad thing to do: serverfault.com/questions/31499/… –  Aaron Weiker Jun 25 '09 at 16:48

3 Answers 3

up vote 3 down vote accepted

There are at least two ways you can handle trying to figure out the size of the database.

  1. Go through a long planning phase where you figure out the expected workload and usage patterns. You then correlate that back to how much disk space per site the quotas allow for. And then you identify how many sites you can support taking into consideration restore time, site performance, and your own comfort level. This should give you an estimated database size that should ideally be 100GB or less. You can then pre-expand your database to the expected maximum size.
  2. Just pre-expand it to 100GB. See this TechNet article.

On top of this you should always be monitoring your database sizes and set up alerts to trigger whenever things look like they could fill up in X days. X will be the time it takes you to not only expand the database, but make sure that it is properly defragmented afterwards and your new restore time figured out. X may also include the time that it takes to add more storage to your SAN/DAS.

The reason I picked 100 GB is because that is inline with the recomended max size of a sharepoint database taken from their documentation. It's not to say that you can't do larger, but need to understand the repurcusions of that choice.

share|improve this answer
    
You may want to also check out this question that was just asked: serverfault.com/questions/31499/… –  Aaron Weiker Jun 25 '09 at 15:05
    
Option 1 is the best, although it is the one that companies are lease likely to invest in :( The two following posts will show you exactly how to figure out how much content currently exists, plan for growth, and size needed disk and I/O: cleverworkarounds.com/2007/10/17/… and cleverworkarounds.com/2007/10/17/… –  Sean Earp Jun 25 '09 at 16:30

Its tough becoming the unwilling DBA. You can set autogrow its just you should try to size your database up front to avoid fragmentation and performance issues with autogrow. Here's some articles by Paul Randal to help you out.

Welcome to the DBA world: http://www.sqlskills.com/BLOGS/PAUL/post/Becoming-an-involuntary-DBA-youre-not-alone.aspx

Sharepoint gold: http://www.sqlskills.com/BLOGS/PAUL/category/Sharepoint.aspx

share|improve this answer
    
Haha not really unwilling just unexpected. I'm actually enjoying it quite a bit and trying to get better at it. –  Sean Howat Jun 25 '09 at 14:35
    
It could be the start of a glittering DBA career :) (Don't turn off autogrow BTW use it as a safety net). –  SuperCoolMoss Jun 27 '09 at 15:43

First, for sharepoint you most certainly do want autogrow turned on. You do want to set a size limit of 100GB (the max recomended sharepoint database size). As you've discovered, sharepoint isn't like a regular database application. A month could go by before someone tries to create a new repository for stuff that uses 10gb, when your usually usage is 10MB a day. Here is a Microsoft doc on what maintenance should be done to a sharepoint database.

share|improve this answer
1  
100GB is not the max SharePoint database size. It is a recommended guideline due to restore SLAs, potential locking issues, etc. –  Sean Earp Jun 25 '09 at 16:26
    
it is the max when there is an issue. PSS was pretty explicit about that when I've called. There will havce to be a really really good business reason before I let any of my sharepoint databases grow beyond 100GB –  Jim B Jun 25 '09 at 18:55
    
I sit right next to the CSS SharePoint escalation team :) From the Official Microsoft SharePoint Team Blog and Joel Oleson no less(blogs.msdn.com/sharepoint/archive/2006/08/03/…) "There are no size restrictions built in... Properly configured WSSv3 and MOSS 2007 installations should be able to handle TB sized content DBs" The recommendation (per the sizing guidelines here: technet.microsoft.com/en-us/library/cc262787.aspx) is of course 100GB, and as you say, it would take a heck of a business case to change my mind :) –  Sean Earp Jun 25 '09 at 22:59

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.