November 2, 2010 at 7:41 am
Hi,
Over the weekend we have updated our OS with the latest patch (Windows Server 2003 R2 Data Center x64Edition SP2 Build 3790). This box is dedicated to a Microsoft SQL Server 2005 (9.00.3282.00 (X64) Standard Edition (64-bit))
The sever has 16GB of memory. The min server memory is set to 6000 and max server memory to 10000. Yesterday we got this warning "Warning: unable to allocate 'min server memory' of 6000MB".
This is the first time we have this in 3 years of life of this server. What this means, we have plenty of memory on this box ? Is there an action I should take? Should I be concerned?
Thanks
November 2, 2010 at 8:21 am
Check if the System is recognizing all the memory installed. You may use to get that information using Task Manager.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 2, 2010 at 8:34 am
The total physical memory in K seen in Task Manager is 16771100. This means it's ok, right?
November 2, 2010 at 8:51 am
It seems correct. How much memory sqlservr.exe is using now? If it is using more than 6000 MB, I would safely ignore this error message.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 2, 2010 at 8:59 am
As of now, sqlservr.exe is using 4,732,828K.
I know that SQL Server is not guaranteed to allocate the amount of memory specified in min server memory. If the load on the server never requires allocating the amount of memory specified in min server memory, SQL Server will run with less memory.
Not sure what is this message. IS it SQLServer was trying to request more memory and the request was denied by the OS?
November 2, 2010 at 9:11 am
Not sure what is this message. IS it SQLServer was trying to request more memory and the request was denied by the OS?
When SQL Server started it tried to acquire 6000MB of RAM as configured. Since it was unable to get the configured minimum memory, that information is logged.
I had seen similar error on the server on which one of the RAM slots had gone faulty. In your case since the server is recognizing all the memory installed, I would not worry much about this warning message.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 2, 2010 at 9:51 am
But this message appears ore the 24 hours after the restart of the SQL Server, not at the time of the restart itself.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply