March 16, 2015 at 6:48 am
We have our sharepoint production on sql 2012 with 2008 server. Whenever this machine is patched, the SQL instance can take over 3 minutes to start up, and it seems to have needed manual intervention to get it going the last few patch cycles.
I can't see anything thrown in the system logs or event logs for SQL. Is this an expected behavior with a sharepoint farm?
March 16, 2015 at 7:11 am
Just guessing, but...
What is tempdb sized at?
Do you have instant file initialization enabled? To do this, the SQL Server service account needs to be granted "perform volume maintanance tasks" permissions in the local security policy.
And, I know this, but I don't remember it, I'm pretty sure that this is not unusual for SharePoint.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
March 16, 2015 at 7:20 am
Hmm.... good question. Is there a recommended size of tempdb as a % of the rest of the size of the farm databases?
Right not its not overly large, initial size is 38 mb db, 10 mb log autogrow by 10%.
Tempdb is also on a different storage than the rest of the user databases in the farm.
Also, I seem to be unable to find where to set the timeout value for the initial startup connection, I'd like to bump it up to see if that will at least be enough to get the service starting on its own after reboot.
March 16, 2015 at 8:03 am
also how many VLF's are there?
run DBCC LOGINFO on your Sharepoint database; you might need to reduce them.
Lowell
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply