Bob,
We have a SQL 7.0 database that frequently runs out of memory and crash's, the
system has a GIG of RAM and is set up with the default memory settings.
I'm seeing an increase in the amount of memory used by the process called
SQLSERVR.EXE and to date I haven't seen it release any, just playing around with
the Enterprise Manager increases the amount of memory in use by the process and
in the past hour it hasn't dropped.
We are adding a lot of data to the system currently through a front end app that
uses named pipes, have you run into this problem at all?
Bob Pfeiff wrote:
> The SQL Server will cache data and query plans and maintain them in cache
> for performance reasons. There are memory management processes in SQL
> Server to decide when to clear items from cache based on aging and on other
> memory requirements on the system. Unless you're processes are doing
> operations like loading an entire large table in cache (e.g., select * from
> somebigtable), I wouldn't expect it to dominate the server's memory.
>
> There is a configuration option to set the maximum amount of system memory
> that SQL Server will use, but you shouldn't have to set it unless the SQL
> Server is regularly monopolizing memory resources at the expense of other
> applications or the OS.
> --
> Bob Pfeiff
> MCDBA, MCSD, MCSE, MCT, SQL Server MVP
> Practice Leader, Data Management
> CIBER, Washington, DC
