471,119 Members | 1,136 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,119 software developers and data experts.

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

Jul 20 '05 #1
3 5460
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" <to*****@myprivacy.ca> wrote in message
news:cb********************@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

Jul 20 '05 #2
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" <sq*************@shadhawk.com> wrote in message
news:e7**************@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" <to*****@myprivacy.ca> wrote in message
news:cb********************@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


Jul 20 '05 #3
Fer
1
Dear reader,

I have the same problem!! My sqlservr.exe in the taskmanager is growing everyday.
The SQL is clustered.
Some times the user is loosing connection and I have a eventID 2020 in my eventviewer.
Microsoft writes to do some registry adjustments in the
hkey_local_machines\system\Currentcontrolset\contr ol\session\mamager\Memory Managent

Create PoolUsagemaximum
and
PagedPoolSize

see http://support.microsoft.com/default...b;en-us;312362


Is there anyone who has another suggestion for this problem??
Or is the Microsoftsolution the only one.
Jun 13 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

11 posts views Thread by jong | last post: by
2 posts views Thread by Arthur M. | last post: by
2 posts views Thread by rizjabbar | last post: by
1 post views Thread by nazgul | last post: by
2 posts views Thread by =?Utf-8?B?Um9oaXQ=?= | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.