Re: memory utilization

From: Thomas Moy (tomoy64_at_myprivacy.ca)
Date: 05/18/04

  • Next message: Tom L: "Re: problem with bcp format file" 
    Date: Tue, 18 May 2004 08:53:10 -0700

    This makes sense. I'll take a couple pills, hold off rebooting and see if
    it behaves properly.

    Thanks for the suggestion.

    Tom

    "Andrew J. Kelly" <sqlmvpnoooospam@shadhawk.com> wrote in message
    news:e7YZdiHPEHA.2876@TK2MSFTNGP09.phx.gbl...
    > SQL Server will use all the ram that it thinks it can up to it's max.
    From
    > there it will dynamically allocate as it sees fit but it will not release
    > any back to the OS unless it specifically calls for it. So your behavior
    > does not seem uncommon. I would hold off rebooting and see if it happens
    > again. If you are running other apps on the same server you may still see
    > some completion for ram but you should not starve it.
    >
    > --
    > Andrew J. Kelly SQL MVP
    >
    >
    > "Thomas Moy" <tomoy64@myprivacy.ca> wrote in message
    > news:cbqdnRae09adgzTd4p2dnA@giganews.com...
    > > What do people think is normal for memory utilization? I know that's
    too
    > > broad, so here are some basics.
    > >
    > > MS SQL Server 2000, Windows 2000 Server, 2GB RAM
    > > Db 1, size = 2.0 GB
    > > Db 2, size = 300MB
    > > Db 3, size = 50MB
    > > Db 4, size = 30MB
    > > Db 5, size = 30MB
    > >
    > > Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
    > slowed.
    > >
    > > Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
    > > Sun 61MB
    > > Mon 200MB
    > > Tues 800MB
    > > Wed 1,124MB
    > > Thu 1,424MB
    > > Fri 1,303MB
    > >
    > > I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
    > > unable to allocate from the system paged pool because the pool was
    empty."
    > > Then I did several updates to address this and got more RAM. I haven't
    > seen
    > > the errors since, but I haven't waited for them to happen: I'm rebooting
    > > every week now. The memory numbers make me suspect SQL Server.
    > >
    > > Scratching my head. Not sure if my problem is gone, and this is normal
    > SQL
    > > Server 2000 behavior, or if my problem is still lurking and I've only
    > muted
    > > it a bit.
    > >
    > > Any thoughts greatly appreciated.
    > >
    > > Tom
    > >
    > >
    > >
    >
    >

  • Next message: Tom L: "Re: problem with bcp format file"

    Relevant Pages

    • Re: memory utilization
      ... SQL Server will use all the ram that it thinks it can up to it's max. ... there it will dynamically allocate as it sees fit but it will not release ... I would hold off rebooting and see if it happens ...
      (microsoft.public.sqlserver.server)
    • Re: memory utilization
      ... SQL Server will use all the ram that it thinks it can up to it's max. ... there it will dynamically allocate as it sees fit but it will not release ... I would hold off rebooting and see if it happens ...
      (microsoft.public.sqlserver)
    • Perpetual Reboot of a Windows 2003 Server DC
      ... I’ve tried running CHKDSK /F and rebooting, but I get the same effect. ... I do see two that are set to restart the box: ... I’m primarily concerned with losing my domain, so I’ve run up a virtual machine, joined it to my domain, and now ready to make the virtual machine my BDC to preserve my domain. ...
      (microsoft.public.windows.server.general)
    • Re: memory utilization
      ... Tom ... > SQL Server will use all the ram that it thinks it can up to it's max. ... I would hold off rebooting and see if it happens ... The memory numbers make me suspect SQL Server. ...
      (microsoft.public.sqlserver.server)
    • Re: access adp, sql server and recordsets
      ... Since the issue only occurs on remote SQL Server. ... A rebooting of machine after security patches may have resolved ... machine hosting Access program to test if you encounter the similar issues ... you may want to creast a new ADP and database on the SQL ...
      (microsoft.public.access.adp.sqlserver)
    Loading