April 21, 2008 at 2:18 pm
What happen to the memory held by the cursor allocated by the process which get killed upon a deadlock?
Is it free by SQL server or it become a "memory leak" ?
Url from the MS doc would be appreciate if you happen to have it. (Still looking for it)
SQL Server 2000 Sp4 (2039)
Thks
April 22, 2008 at 12:42 pm
It should be released just like any other terminated process. Do you have reason to believe otherwise?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
April 22, 2008 at 1:10 pm
Yes
We have a memory leak and it's closely related on code which use cursors and is the victim's deadlock.
Before jumping to conclusion I'm searching for information on this topic.
A deadlock kill the process but cursor need to be deallocate to free all its memory.
If the deallocate is not called, locks held by the process are freed but not the memory held by the cursor itself. Hence my question when a deadlock occur.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply