we are running sql server 2008 (not R2). 64 bit machine/operating system - 32 gig memory. The hardware/system guys are using Orion, I use Idera to monitory system vitals. Orion refers to "Physical Memory Size" Idera uses the term "Available Memory". Right now they both show about 4 gig. Summing the memory usage of all proceses comes to around 3.5 gig so the sytem looks OK.
The sys guys are concerned because Orion always shows 32 gig 'physical memory' until this last op sys patch. After reboot that variable started displaying the 4 gig. They think something is wrong. (no reports of performance loss, no issues with any vital stats).
The min and max are set to 24 gig. SQL Server uses only what it needs. however if min is set to max, once the min is reached mem allocation will never drop below min. (Right?). However, it looks to me like our system never even gets close to min. BOL (and others) talk about a 'DataBase Server Load shortly after startup' to get to that min to grab that space for SQL Server so no other process can have it. (That's what we want its a dedicated server to that instance of sql server).
THE QUESTION: What is a database server load and how do I implement it?
Thanks, Pete Mottershead Senior DBA Central States Indemnity Omaha, NE.