memory utilization

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
Are there other applications (IIS) competing for memory on this server?
|||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
>
>
|||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[vbcol=seagreen]
> 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...
too[vbcol=seagreen]
> slowed.
empty."
> seen
> SQL
> muted
>