Link to home
Start Free TrialLog in
Avatar of compdigit44
compdigit44

asked on

Sharepoint 2010 and SQL 2012

I have try to tune our SQL 2012 server which host our SharePoint 2010 environment. I am not a DBA so please bare with me.

I have read that when SQL is hosting content for SharePoint you should disable auto-create stats and set the fill factor to 80.

How and where can I check the current setting for these values.
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

Fill Factor


The auto-create isn't on by default.
Avatar of compdigit44
compdigit44

ASKER

Do you have any additional items I should do in sql 2012 hosting sharepoint DB's to make ensure top performance
ASKER CERTIFIED SOLUTION
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Rainer Jeschor
Hi,
have no link at hand BUT the MOST important performance killer is to setup the TEMPDB the wrong way.
During each and every request a lot of temporary objects/tables are created on SQL side - all this objects are written to the tempdb. Therefore normally the most workload is on the tempdb.

Just my 2ct
Rainer
I was planning on moving my tempdb to it's own volume. What are your thoughts on change the fill factor setting or DB defragging?
For larger farms I go ahead and do it, but for most smaller farms, it doesn't make a difference.  It's not going to hurt through, for anyone to do it.

For SharePoint 2013 I believe the fill is different than 80.  But you don't care bout that right now :)
Thansks!!! How can you tell if changing the fill factor would help or not?

Should the db be defragged regually?
SharePoint will defrag db's.  Make sure you read the db maintenance article on Technet.