|
|
Posted by Dave on 11/04/05 00:06
I was trying to find the bottle neck on our server while we were
running a couple very large updates.
I ran the following query and noticed there were a couple sleeping
spid's that were really eating up the memory. One had a value of
16000.
I guess my question is was this query still holding on to that memory
even though the query had finished? Why didn't SQL Server clean it up?
select spid
,substring(Loginame,1,10) Login
,memusage
,substring(hostname,1,15) Host
,program_name
,cmd
,status
from master..sysprocesses
order by memusage desc
Navigation:
[Reply to this message]
|