SBSMonitoring/SQL Memory allocation error (run away Memory usage)

Discussion in 'Windows Small Business Server' started by David Gill, Sep 20, 2005.

  1. David Gill

    David Gill Guest

    SBSMonitoring MSDE has sprung a memory leak or something within the last
    week.
    The dang thing is blimping over a Gig of RAM, if I restart it, she returns
    to normal, 30 megs, for a few hours then starts growing rapidly.
    The server has all the latest patches, SBS SP1,Windows2003 SP1, SQL MSDE
    SP4, SQL2000 Std edition SP4, Exchange2003 SP1.
    Any ideas what is causing this and how to fix it, besides stopping and
    restarting the service?
    Thanks
     
    David Gill, Sep 20, 2005
    #1
    1. Advertisements

  2. Hi,

    Thanks for posting here!

    For your description, I understand that your concern is that if there is a
    memory leak issue when the MSSQL$SBSMONITORING service run. If I am off
    base, please don't hesitate to let me know.

    Based on my research most cases, this is a normal behavior. Since SBS 2003
    server is an integrated product, some services such as Exchange Information
    store, ISA web proxy service or SQL Server will normally use large memory.

    1. SQL Server is designed to use memory. It caches data and query plans to
    memory so that it will be able to quickly access data. All relational
    database management systems do this. Unless you are experiencing problems
    because of the high memory usage from SQL Server, I would not worry.

    When you start SQL Server, SQL Server memory usage may continue to steadily
    increase and not decrease, even when activity on the server is low.
    Additionally, the Task Manager and Performance Monitor may show that the
    physical memory available on the computer is steadily decreasing until the
    available memory is between 4 to 10 MB.

    This behavior alone does not indicate a memory leak. This behavior is
    normal and is an intended behavior of the SQL Server buffer pool.

    By default, SQL Server dynamically grows and shrinks the size of its buffer
    pool (cache) depending on the physical memory load reported by the
    operating system. As long as enough memory is available to prevent paging
    (between 4 - 10 MB), the SQL Server buffer pool will continue to grow. As
    other processes on the same computer as SQL Server allocate memory, the SQL
    Server buffer manager will release memory as needed. SQL Server can free
    and acquire several megabytes of memory each second, allowing it to quickly
    adjust to memory allocation changes.

    For more information, please see the article below:

    321363 INF: SQL Server Memory Usage
    http://support.microsoft.com/?id=321363

    2. However, we can use max server memory to prevent SQL Server from using
    more that the specified amount of memory (we can also use min server memory
    to guarantee a minimum amount of memory to an instance of SQL Server). To
    do so, open a command prompt and run the following command:

    osql -E -S sbsserver\<instance name>

    You will enter the osql command prompt. Run the commends below (replace
    <xxx> with the amount of memory):

    1> EXEC sp_configure 'show advanced options', 1
    2> reconfigure
    3> go

    1> EXEC sp_configure 'min server memory', <xxx>
    2> reconfigure
    3> go

    1> EXEC sp_configure 'max server memory', <xxx>
    2> reconfigure
    3> go

    After doing the above steps, you may run the commands to check the
    configured memory usage:

    1> EXEC sp_configure
    2> go

    Hope this helps. Try to test to see if thing turn to be better.

    Please feel free to let me know if you have any further concerns or
    questions regarding the issue. I am looking forward to your reply!

    Have a nice day!

    Best Regards,

    Jenny Wu
    Microsoft CSS Online Newsgroup Support
    Get Secure! - www.microsoft.com/security
    ======================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    ======================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
     
    Jenny wu [MSFT], Sep 21, 2005
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.