| Jasper Smith 2002-11-29, 9:23 pm |
| This behaviour is by design. Since you are also running
IIS on this server it will probably be worth setting a max
limit on the memory SQL can use to prevent IIS running low
(ideally they would be on separate servers). Have a look at
Memory Architecture in BOL. Also this KB article
http://support.microsoft.com/defaul...b;en-us;q321363
Basic point is SQL will not free up memory unless it REALLY
is forced to because keeping pages in memory allows much
more efficent access than peforming physical IO.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jay" <jay.lindsay@mckesson.com> wrote in message
news:202ce01c2980f$647696a0$89
f82ecf@TK2MSFTNGXA01...
> I have been monitoring available memory on our web
> server. The server has 1 gig mem. When I re-boot the
> server there is about 850 meg of available memory.
> Available memory gradually decreases. After the server
> operates for only a few days the available memory was
> reduced to 200meg. I discovered that SQL Server was taking
> 500 meg of memory.
>
> Questons:
>
> How can I determine what SQL Server action is taking up
> the memory?
>
> Why is SQL Server not releasing the memory. I made a
> recent check on the available memory during the holidays
> when use of our web server was very low. SQL Server had
> not released the memory. Of course, SQL Server is doing
> other things besides servicing our web server such as
> backups.
>
> Is there a way I can "manually" release the memory SQL
> Server has grabbed without re-booting the server. I did
> not try just stopping and starting SQL Server. I would
> like to be able to do something to force a release of
> memory without stopping anything.
>
> Thanks for you help.
>
> Jay
|