March 19, 2008 at 6:02 pm
I have just experienced the same problems with the messages of paing in sql.
64 GIG RAM and the paging when to 32 GIG after one DBCC CHECKDB on 40 gig table.
64 bits, enterprise
So i did the lock in pages in memory.
I set the min memory to 8196 and max to 50 gig (set this to what you have).
Before i had min set to 0.
This fixed it ...without the min memory i could produce the PF every single time. Start, stop sql then run dbcc checkdb would always page from 1.4 GIG to 32 GIG.
Hope that my help you.
What is the tokencache? and 200 mb is something i will look at.
Any more explanation on what hte tokencache is be great.
March 20, 2008 at 7:42 am
I found our issue was that I took for granted that as a member of the Local Administrators group, the SQL service was implicitly granted the right to lock pages in memory. This is not the case, you must explicitly set that right for the service account. We also set min and max memory for SQL to 13GB (out of 16) and have another 16 on order.
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
March 20, 2008 at 8:06 am
Per Microsoft (sorry, can't find a link) you should not set min and max memory equal. I recommend leaving a GB between them. Something about SQLOS internal memory functionality needing some space.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
March 20, 2008 at 8:11 am
Thanks Guru, will do.
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
March 20, 2008 at 9:07 am
The min and max being same i.e min should be 49 GIG and MAX 50 GIG
Hmmm thats interesting.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply