Home Forums SQL Server 2005 Administering new 64-bit Sql 2005 Server - integrity check completes then memory spikes 75% and doesnt lower RE: new 64-bit Sql 2005 Server - integrity check completes then memory spikes 75% and doesnt lower

  • oraculum (8/19/2009)


    Still think i'm being misunderstood, the memory allocated is 24GB this is fine and as expected as its the Max Server Memory...

    The problem is that 75% of that 'allocated' memory is constantly being used i.e. 18GB is in use now by sql server, even though nothing is running. If you look at perfmon logs the sql memory in use never drops on this server..

    Server 32GB

    SQL Allocated 24GB

    SQL In Use 18GB ??

    OS is not using more than a couple ever, and it has 8GB to itself anyhow...

    Nope, you are not being mis-understood. That is normal behavior for SQL Server - and the 18GB of usage is for the buffer pool. SQL Server reads the data from the database into memory - and accesses that data from memory. The more memory that is available, the more SQL Server will allocate for the buffer pool and load.

    The fact that you have set the max memory for the server to 24GB - and SQL Server is only using 18GB at this point tells me that you might not need more than 18GB of memory for this instance of SQL Server.

    Again, that is normal behavior and expected for SQL Server.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs