XPost: microsoft.public.sqlserver.programming   
   From: esquel@sommarskog.se   
      
   Gene Wirchenko (genew@ocis.net) writes:   
   >   1) The odd memory behavour is that SQLSERVR.EXE is taking about   
   > 600MB doing nothing!  Does it ever release memory?  Sure, I was doing   
   > something yesterday.   
      
   Yes, if someone else needs it. But SQL Server is designed to grab as much   
   memory as it can. Reading data from the cache is so much faster than reading   
   from disk.   
      
   You can use sp_configure set to the max amount of memory for the buffer   
   pool. On a developer machine, this can be a good idea to avoid that SQL   
   Server inflates too much so that other things you are not using for the   
   moment are swapped out.   
      
   >   2) There are a lot of 368 byte files in C:\Documents and   
   > Settings\LocalService\Application Data\Microsoft\Protect\S-1-5-19.  By   
   > a lot, I mean millions.  By "millions", I mean exactly that.  This is   
   > no exaggeration.  Defrag reports about 5.5M files on my system.   I   
   > can not run chkdsk /f on my C: drive at boot and have it take less   
   > than hours to run.   
      
   Any particular reason you suspect SQL Server? Have you looked inside of   
   these files?   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Books Online for SQL Server 2005 at   
   http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx   
   Books Online for SQL Server 2000 at   
   http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)