Re: SQL Server 2000 SP4: Memory leak or normal performance?

Tech-Archive recommends: Fix windows errors by optimizing your registry



The Chicago Wolf,

SQL Server will use any available memory that it can to optimize its own
performance, so 65 MB is just what it needs when it first gets started. SQL
Server makes heavy use of memory caches, so that is why additional memory is
being used taking you up to 1.7GB. Any data or procedures cached in memory
already reduce I/Os , which usually improves performance.

However, if there is pressure for memory from other applications, SQL Server
can automatically start giving up some of that memory to the other
applications. You can also set the SQL Server to use a MAX amount of memory
if that is necessary. This is most commonly done if a machine is running
more than one instance of SQL Server or there are other major processes
which need to have memory saved for them.

So, in general, everything is just fine. You have to decide if it is
causing you any real problems and what to do about that. For most users,
letting SQL Server dynamically manage memory is the best choice.

RLF


"Thee Chicago Wolf" <.@.> wrote in message
news:lisb14hpojp2ron0ihr8deenbl0m6jpj1n@xxxxxxxxxx
Hey all, first posting here. Did some checking around on Google for
this issue before asking here but so far am coming up with no clear
idea.

Have W2K3 Server SP2 (4GB RAM) with SQL Server 2000 SP4 and am
noticing sqlserver.exe gobbling up 1.7GB+ RAM. Two days ago I rebooted
the server for general updates and sqlserver.exe was only using 65MB.
Two days later, 1.7GB+!? Does that seem even remotely right? In doing
more research I came upon KB916287 but have yet to apply it. No
mention of it fixing any memory leaks either. I can't find anything
that elaborates on the included fixes other than what's individually
mentioned in KB894905. Anyone experience the same stuff I am? Any tips
would be great.

- Thee Chicago Wolf

- Thee Chicago Wolf


.



Relevant Pages

  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Consolidating instances of SQL server
    ... SQL Server is designed to use memory. ... The maximum amount of memory SQL Server can use varies depending on your ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: The DBMS returned an unspecified error.
    ... | We are using Microsoft's JDBC driver for Java database access to SQL ... | Insufficient memory available. ... even though SQL Server 2000 is configured to use up to the ... the problem is most likely in the MemToLeave ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: multiple instances of sql - 2 Gb memory limitation?
    ... The 2GB Memory limitation is per instance and the SQL Server can be ... Configure memory for more than 2 GB in SQL Server ... Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter ...
    (microsoft.public.sqlserver.server)