memory usage issues

the memory usage on our SQL 2000 server keeps creeping up to near 1.5 gig
out of 2.5 gigs. is this normal? is there a way to prevent this? should it
be controlled somehow?From BOL:
--snip
To acquire as much memory as possible without generating excess paging I/O,
each instance of SQL Server sets a target of acquiring memory until free
physical memory on the computer is in the range of 4 MB to 10 MB. This range
was chosen because testing has shown that Windows NT and Windows 2000 have
minimal memory swapping until the memory allocations equal the available
physical memory minus 4 MB. An instance of SQL Server that is processing a
heavy workload keeps the free physical memory at the lower end (4 MB) of the
range; an instance that is processing a light workload keeps the free memory
at the higher end of the range (10 MB).
--snip
This behavior is expected and is designed for maximum performance on a
dedicated SQL server.
--
Geoff N. Hiten
SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"harun kazi" <kazi[RemoveThis]@.wideopenwest.com> wrote in message
news:OqgYjHOYDHA.1736@.TK2MSFTNGP10.phx.gbl...
> the memory usage on our SQL 2000 server keeps creeping up to near 1.5 gig
> out of 2.5 gigs. is this normal? is there a way to prevent this? should it
> be controlled somehow?
>|||thank you both.
"harvinder" <hs@.metratech.com> wrote in message
news:001b01c360e4$282db540$a301280a@.phx.gbl...
> sql server will like to take most of the memory if
> required and no other process need memory... generally it
> is good idea to leave it this way(dynamic)...but if u
> want to have control over memory usage u can change the
> parameter max memory from EM or QA.
> Thanks
> --Harvinder
> >--Original Message--
> >the memory usage on our SQL 2000 server keeps creeping up
> to near 1.5 gig
> >out of 2.5 gigs. is this normal? is there a way to
> prevent this? should it
> >be controlled somehow?
> >
> >
> >.
> >|||Additionally SQL will not release memory ( even if no one is logged in)
unless there is < 5 ( between 5 and 10 ) MB of free memory... Why work to
reduce memory utilization if there is no need?
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and its
community of SQL Server professionals.
www.sqlpass.org
"harun kazi" <kazi[RemoveThis]@.wideopenwest.com> wrote in message
news:OqgYjHOYDHA.1736@.TK2MSFTNGP10.phx.gbl...
> the memory usage on our SQL 2000 server keeps creeping up to near 1.5 gig
> out of 2.5 gigs. is this normal? is there a way to prevent this? should it
> be controlled somehow?
>|||And just to hammer it home :-)
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"harun kazi" <kazi[RemoveThis]@.wideopenwest.com> wrote in message
news:OqgYjHOYDHA.1736@.TK2MSFTNGP10.phx.gbl...
the memory usage on our SQL 2000 server keeps creeping up to near 1.5 gig
out of 2.5 gigs. is this normal? is there a way to prevent this? should it
be controlled somehow?

Memory Manager

The CPU pegged on a production server this morning. There is a warning
message in the log. I'm not sure what it means. Or what to do to prevent it
in the future.
Date 1/23/2008 4:11:36 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source spid3s
Message
Memory Manager
VM Reserved = 8521512 KB
VM Committed = 8504536 KB
AWE Allocated = 0 KB
Reserved Memory = 1024 KB
Reserved Memory In Use = 0 KB
Then later on
Date 1/23/2008 4:11:36 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source spid3s
Message
MEMORYCLERK_SQLGENERAL (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 28920 KB
MultiPage Allocator = 4888 KB
Still later
Date 1/23/2008 4:11:36 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source spid3s
Message
Buffer Counts: Committed=1032192 Target=1047941 Hashed=608946
Internal Reservation=209588 External Reservation=1297
Stolen Potential=571000
Min Free=128 Visible=1047941
Available Paging File=858726400
Finally:
Date 1/23/2008 4:12:19 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source Server
Message
***Stack Dump being sent to D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump0008.txt
--
Regards,
JamieProbably time to call Microsoft tech support. Or scan the bug fix lists for
all patches you don't have on your server to see if one of them addresses
the symptoms you are seeing.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B2F823A0-5AB3-4EF6-8F16-D515052F7DE4@.microsoft.com...
> The CPU pegged on a production server this morning. There is a warning
> message in the log. I'm not sure what it means. Or what to do to prevent
> it
> in the future.
> Date 1/23/2008 4:11:36 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source spid3s
> Message
> Memory Manager
> VM Reserved = 8521512 KB
> VM Committed = 8504536 KB
> AWE Allocated = 0 KB
> Reserved Memory = 1024 KB
> Reserved Memory In Use = 0 KB
>
> Then later on
> Date 1/23/2008 4:11:36 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source spid3s
> Message
> MEMORYCLERK_SQLGENERAL (Total)
> VM Reserved = 0 KB
> VM Committed = 0 KB
> AWE Allocated = 0 KB
> SM Reserved = 0 KB
> SM Committed = 0 KB
> SinglePage Allocator = 28920 KB
> MultiPage Allocator = 4888 KB
> Still later
> Date 1/23/2008 4:11:36 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source spid3s
> Message
> Buffer Counts: Committed=1032192 Target=1047941 Hashed=608946
> Internal Reservation=209588 External Reservation=1297
> Stolen Potential=571000
> Min Free=128 Visible=1047941
> Available Paging File=858726400
>
> Finally:
> Date 1/23/2008 4:12:19 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source Server
> Message
> ***Stack Dump being sent to D:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump0008.txt
>
> --
> Regards,
> Jamie