October 26, 2009 at 1:16 pm
To me, those metrics would indicate memory pressure. How big is your database? What do your Target Server Memory and Total Server Memory look like? Also, is the page file getting used?
October 26, 2009 at 2:51 pm
Thanks,
These are the Share point databases. We have 10 Databases and the biggest database size id 20 GB and the rest are <2GB
How could I Know whether page file used or not. We are using the default page file size. And it is a A/A/P cluster setup.
October 27, 2009 at 11:56 am
When ever I restart the SQL Service, I'm getting the below message in the error log:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 38876, committed (KB): 105728, memory utilization: 36%.
Is that normal to get the above error every time when the SQL instance restarts??
October 28, 2009 at 8:17 am
1) checkdb is VERY IO intensive, so I would expect to see indications of IO/Memory pressure during it's execution
2) There are MANY things that can interplay to cause memory to be paged out - cluster instances being on the same machine, other applications, memory settings, file operations in windows, etc, etc. I recommend you get a professional to hook up to your system to give it a review. You could be going back and forth here for days or weeks without finding a cause.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
October 28, 2009 at 9:54 am
Try enabling "Lock Pages In Memory" and setting Max Memory to an appropriate number. Is the Page Life Expectancy counter consistently below 300 or was that just a spike? You can check The Paging File object's % Usage and % Usage Peak to see how extensively the page file is being used.
Viewing 5 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply