June 25, 2009 at 11:08 am
I have inherited a server, at a new job, that is running Windows Server Std Ed 2003 SP2 X64 and 4 instances of SQL Server 2005 SP3 Developers X64, with 8GB of physical memory. The memory settings are as follows: default-4GB(max) 1GB(min);instance 2-4GB(max) 1GB(min);instance 3-2GB(max) 1GB(min);instance 4-1GB(max) 512MB(min). When the server boots ups The instance 2 memory goes right up to what the max is set(It was at 6GB to start with and still maxed out). The default instance will peak at 4.3GB and then stays around 1.4GB, instance 2 goes straight to 4.2GB peaking at 4.3GB and stays there. Instance 3 gets to 900MB and stays there and instance 4 stays around 150MB. The reason I state that instance 2 doesn't give back memory is that we have had some restores running on anther instance that just crawled and when we stopped and restarted instance two the restores quickly finished. I have two questions 1) It is said that SQL will dynamically give back memory when the OS or other applications need memory but does that include if another instance needs it? 2) (and the most important to me) What fills up the memory and how can someone look to see what is in there? Please let me know if there is a book I need to buy or other articles to read, but if some one could at least get me pointed in the right direction I would greatly appreciate it. One last comment, could this be a problem because we are on developer edition? We have a production setup similar to this (I have been told this and have not been able to examine it) that is on Enterprise Edition and it doesn't seem to have these symptoms.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply