Re: Why the memory usage of SqlServer doesn't go down

Hi Stu,

I got you point. Because after we exit our system, there is no memory
issues , SQLServer can just hold 512M memory. To be simple, SQLServer
always tries
to keep all acquired memory until OS runs out of memory and asks it to
relinguish
some to other applications.

Thanks !

Jennifer,

Stu wrote:
Not trying to be harsh, but you thought wrong :) SQL Server won't
release the memory back to the min configuration until Windows needs
it; are you having memory issues?

Stu


Jenniflower wrote:
Hi Gurus,

Our system is using SqlServer 2005 on XP.( On my machine,only this
application access SQLServer.) The sqlserver memory is configured to
128MB (Min)~512 MB(Max)

After our system get started, sqlserver takes about 100M memory. After
the system runs for a while, the memory used by sqlserver goes up to
512MB. Then we exit our application and expect the memory usage of
SqlServer could be dropped down to the min value. Unfortunately, it
seems SqlServer never release any memory until we restart it.

I thought dynamic memory configuration means that SQLServer can auto
shrink memory usage if there is no more database accessing. But based
on my observation, SQLserver just holds all the memory . :( How can
we let the sqlServer shrink the memory usage accordingly to workload?


I do appreciate for your help!

Best regards,



Jennifer

.

Relevant Pages

  • Re: Available Scsi Bandwidth
    ... yes, SQLServer is really IO bound, but when you have enough memory, this will be memory IO instead of disk IO, so you could say that SQLSErver is a memory intensive application instead of an IO intensive application. ... No matter how fast you disk and disk controllers are, ... the controllers you mention have a 2Gb/sec per channel peak bandwidth. ...
    (microsoft.public.windows.server.general)
  • Re: Available Scsi Bandwidth
    ... will be memory IO instead of disk IO, so you could say that SQLSErver is a memory intensive application instead of an IO intensive application. ... No matter how fast you disk and disk controllers are, ... In an optimum situation, SQLServer only needs the disks to for inserts, updates and deletes, not for selects. ... the controllers you mention have a 2Gb/sec per channel peak bandwidth. ...
    (microsoft.public.windows.server.general)
  • Memory usage with linked servers
    ... I have written an OLEDB driver that acts as a linked server within SQL2000 ... SQLServer memory usage in task manager will go up. ... you would expect, however, if I issue the same query again then SQLServer ...
    (microsoft.public.data.oledb)
  • Why the memory usage of SqlServer doesnt go down
    ... Our system is using SqlServer 2005 on XP.(On my machine,only this ... sqlserver takes about 100M memory. ... I thought dynamic memory configuration means that SQLServer can auto ... shrink memory usage if there is no more database accessing. ...
    (comp.databases.ms-sqlserver)
  • Re: Why the memory usage of SqlServer doesnt go down
    ... release the memory back to the min configuration until Windows needs ... Our system is using SqlServer 2005 on XP.(On my machine,only this ... I thought dynamic memory configuration means that SQLServer can auto ... shrink memory usage if there is no more database accessing. ...
    (comp.databases.ms-sqlserver)