We are running SQL 2005 STANDARD edition on a 64 bit Clustered box.
I've been dealing with this problem for several months, and have yet to find a solution on this..any help is appreciated. As I've seen in other posts, I agree that this is a bug of the Standard Edition.
Total of 16gigs of memory
Max_server_memory is throttled to 14 gigs
We are running NO other applications on this box, other than a couple of services, etc¬hing that consumes memory.
Here are my questions:
During high traffic, we are seeing this informational message often in the Application log:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 305 seconds. Working set (KB): 1719764, committed (KB): 3611144, memory utilization: 47%%.
Why, if the instances arent even close to the max server memory setting, and the OS has plenty of memory to work with (usually 7-9 gigs), is SQL Server dumping memory back to the OS? We are DEFINITELY seeing performance degradation during the moment of memory release.
We are thinking of bringing min_server_memory up close to the max, if not equal&but first I am working with some counters during high traffic to see how much memory we are utilizing at any given time&.is min_server_memory = max_server_memory a good idea?
Note: We cant lock pages in memory on SQL due to the fact that we dont have enterprise edition.