I know this is 3 months old but the answer is just wrong. SQL Server
should be setup to dynamically use memory, which is what appears to be
happening. When the ETL process needs more RAM it asks Windows which
duly allocates until all RAM has been used. SQL Server does not
automatically return the memory unless Windows explicitly asks for
blocks of memory. If Windows does not need the memory then SQL server
keeps it. This is by design and makes logical sense on a SQL box after
all who else wants the memory. No-one, so why keep sending messages
between SQL and Windows asking for more memory one minute and then
handing it back the next. Overhead NOT REQUIRED.
Adrian
[quoted text, click to view] Nate Shedd wrote:
> You may be allowing SQL Server to use too much memory on your server. We had
> a similar problem with processing Analysis Services cubes. On the SQL Server
> Properties dialog Memory tab, set the Maximum (MB) to less than the full
> amount. For example, if the slider has a range from 4MB to 2048MB, you could
> set it to 1500MB.
>
> "Orlando" <anonymous@discussions.microsoft.com> wrote in message
> news:1cd5701c45317$f9572e50$a101280a@phx.gbl...
>
>>Hello there, my datawarehouse uses SQL 2000 enterprise as
>>database. When the ETL process runs it takes all the
>>memory of my server (aprox 2gb) and when it finish, the
>>memory stay freeze, an the task manager shows that the
>>MSSQL still using the memory and this takes a long time,
>>so I have to use the NET STOP to free the resources and
>>memory. What can provocate this situation?
>
>