Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2004
    Posts
    91

    Unanswered: Memory footprint

    Hi Everyone -

    Is there a way to have SQL server 2k shrink the memory footprint??

    computer starts up ok, small sql footprint,
    after a little while - the size SWELLS to 230,384K in memory
    usage (according to task manger)

    Is there a way to reduce the footprint size??

    (without stopping and starting the service)???


    thanks
    tony

  2. #2
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Tony ... SQL Server is designed to dynamically manage the memory on the server. Assuming no other processes, it will leave the OS about 5 meg. Then, as the server needs it, it will dole it out. You can modify these settings either thru Enterprise Manager (Server/Properties/Memory) or QA (sp_configure).
    From BOL under memory -> dynamically managing

    [QUOTE]
    Dynamically Managing Memory on Windows NT and Windows 2000When running on Microsoft® Windows NT® or Windows® 2000, the default memory management behavior of the SQL Server database engine is not to acquire a specific amount of memory, but to acquire as much memory as it can without generating excess paging I/O. The database engine does this by acquiring as much memory as is available, while leaving enough memory free to prevent the operating system from swapping memory.


    [QUOTE/]

  3. #3
    Join Date
    Oct 2004
    Posts
    91

    ok

    OK -

    i got that, thank you for the replay -

    but is there a way to FORCE sql server to release
    some of that memory when no one is attached???


    I've tried setting the memory usage in the setup
    of the server - but it just seems to override it and
    do whatever it wants to do -

    no when i restart the service, the memory usage drops
    to a reasonable level - then when the action starts
    it starts to eat ram left and right....

    thanks again for the reply!

    take care
    tony

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    230MB is almost nothing in the SQL server world. Maybe it is OK for a dev machine, but certainly not a production server. What is the problem you are trying to solve? And what proof do you have that this solution (if it works) will solve that problem?

    As for the question, you could try to set auto-close on the user databases. This will close the database files, but I am not certain if it will release any of the memory.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •