March 16, 2010 at 2:08 pm
Greetings all 😀
I am currently working with a new server that have 50GB of memory which is by far the most I have ever had to work with (most ive had is the normal 32bit os 4GB). After a few days of setting things up and testing I realized that sql server was using almost all available memory. After a bit of research I found that SQL Server will consume as much memory as it can whether it needs it or not. So I set an upper limit of 30GB (seeing as none of my databases are larger than 20GB I seriously doubt more than that would be needed).
Another thing I noticed was that the PF usage is about the same as memory usage. Right now I have 38.8GB of pagefile being used on the server, and a total of 40GB of memory is being used.
So my question is twofold; 1) Is that normal PF usage with that much memory being utilized by SQL Server, or should I be changing settings so that it is using memory before the Page File? 2) How would I go about making an assessment of how much memory SQL Server needs on my system so I can set an appropriate upper threshold of memory?
Link to my blog http://notyelf.com/
March 17, 2010 at 7:12 pm
Are you on a 64 bit or 32 bit OS? 64 or 32 bit sql server?
March 22, 2010 at 12:14 pm
64 bit
Link to my blog http://notyelf.com/
March 23, 2010 at 7:29 am
It is normally best to grant the SQL Server process the 'lock pages in memory' right, so SQL Server can use non-paged memory.
If this is Standard Edition, please read the following Microsoft KB article:
To understand memory usage as displayed in Task Manager:
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply