Last week during an event just like this one: http://social.msdn.microsoft.com/Forums/en-US/1ecf3d5a-31e3-4346-9ff7-93b1ff57a3cb/blockedprocessreport-what-is-this-waitresource-object-327671246076970-compile?forum=sqldatabaseengine and again here: http://dba.stackexchange.com/questions/55120/excessive-compile-blocking-on-sp-procedure-params-90-rowset
I noticed that the output of DBCC MEMORYSTATUS only included a section for:
After i had cleared the 'COMPILE blocking' i ran dbcc MEMORYSTATUS again hoping something would show a significant before and after difference. The only difference was that the after MEMORYSTATUS execution included sections for:
MEMORYCLERK_SQLOPTIMIZER (node 1) KB
MEMORYCLERK_SQLOPTIMIZER (node 2) KB
MEMORYCLERK_SQLOPTIMIZER (node 3) KB
MEMORYCLERK_SQLOPTIMIZER (Total) KB
Does this indicate anything? Is it possibly connected to the state of the instance when blocking was happening?
SQL2008r2 Sp2 Cu 8 Standard on Win2008R2
-- dan http://dnhlmssql.blogspot.com/