Post reply

Memory Locking After Script Completed

  • May 28, 2007 at 5:06 am

    #178845

    Hi there,

    When I run scripts on our dedicated SQL 2005 box, the memory usage climbs up pretty high. However, when the scripts have completed, SQL still continues to consume the same amount of memory....? We end up with the situation where we can see absolutely no processes running in the activity monitor, but the sql services is consuming over 4GB of memory...!!??

    Many thanks in advance

    Chris

  • May 28, 2007 at 6:53 am

    #709185

    That is normal behaviour. SQL Server will consume as much memory as it needs, mostly for caching data. It will hold onto that memory until the operating system demands it back.

    Take a read through this and related concepts

    http://msdn2.microsoft.com/en-us/library/ms187499.aspx

    --------------------
    Colt 45 - the original point and click interface

  • May 28, 2007 at 9:12 am

    #709203

    You can limit the total memory SQL Server will use. Out of curiosity, how much memory on the server and what's the SQL Setting.

  • May 30, 2007 at 2:32 am

    #709599

    Hi Guys

    Thanks for your feedback. Regarding SQL holding onto memory........

    Does these mean that if SQL is holding onto 7GB of memory and running no processes, the full 7GB will be available to you if you then run a SQL query?

    Our server has 8GB of RAM, and I have limited SQL to 7GB

    PS We are running the 64 bit version of SQL

     

    Many thanks

    Chris

  • May 30, 2007 at 2:42 am

    #709604

    The short answer, not necessarily.

    The MSDN topic and its related topics will outline how SQL uses memory.

    --------------------
    Colt 45 - the original point and click interface

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply