I have received the email below that states that an alert has been fired and
a significant part of SQL Server process memory has been paged out
should I raise the Minimum server memory to 1740 too?
Microsoft SQL Server 2005 - 9.00.5000.00 (X64) Dec 10 2010 10:38:40 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
There are other applications, even monitoring applications running on that server.
You can have a glimpse of those applications by looking at the picture below.
We received an alert at 12:15:37 PM on the wrsleic1 default instance that "a significant part of SQL Server process memory has been paged out."
We've investigated the alert and found that SQL Server previously reported this condition last year on 13/04/2015. SQL Server is currently allocated a maximum memory of 1.7 GB while the server has 4 GB physical memory available to it (and a dynamically sized page file that is currently 5 GB).
At the time of the alert SQL Server had it's maximum memory reserved while not necessarily actively using the cached data. Therefore when the server detected memory pressures from an external process (potentially IIS but we can't determine this retrospectively), SQL Server trimmed its working set to accommodate the requirement and is currently utilising approximately 900 MB.
The OS is responsible for memory management and SQL Server is designed to respond to memory release requests as it did at the time of the alert. Therefore if there was no perceivable impact to performance on the application that uses the hosted databases on this instance then we don't recommend any further action.
Lock Pages in Memory
The lock pages in memory has not been enabled for any sql server account.
I was going to change this, however, I decided to leave this server as it is because:
1) it is running on standard edition sql server 2005 SP2 and on this page it says
Standard Edition Up until SQL Server 2005 SP3 Cumulative Update Package 4 and SQL Server 2008 SP1 Cumulative Update Package 2 'Lock Pages in Memory' was not supported in SQL Server Standard Edition.
2) after enabling it - needs a reboot according to this page
Question: “Weather we require Lock Pages in Memory in SQL Server 64-Bit”?
3) We should (hope so) migrate this server to sql server 2014 soon
this page has a bit more about lock pages in memory and a reminder: