Hi there

The core design of SQL Server ends up preventing you from changing and/or
manipulating many DBMS engine components, and memory is a big one. What
your trying to do I believe is simply track down why SQL Server is slow
moving to your max memory setting. The memory break down will be mainly the
buffer cache, then the procedure cache, both of which you cant control.
Dont worry about hitting max, the dbms wont lock up, if the internal
algorithms believe more memory is required, it takes it and works with what
it has.

To start with:
a) sysobjects table in tempdb (lots of temp table action etc?)
b) check large batch jobs, dbcc jobs can create lots of activity
c) remember, all IO must be via the buffer cache
d) profile for large adhoc queries

Have fun with this :) if your not happy with the memory consumption, then
simply reduce the max, dont get overly worried about the usage.

Cheers

Ck

-----Original Message-----
From: Kotze, Paul [mailto:[Email Address Removed] Thursday, 30 January 2003 5:18 PM
To: LazyDBA.com Discussion
Subject: RE: RE: Urgent Help needed - SQL2K Memory

MS Sql Server LazyDBA home page