Keith Mescha (12/9/2010)
I have this solution partly implemented. I have recently upgraded quite a few servers to Windows 2008 R2 and SQL 2008 R2 and just found out that the vb script from within SCOM is not writing to the event log. Just started digging but figured I would ping this forum to see if anyone has noticed this behavior.If you have appreciate any direction. When I find the cause I'll be sure to post back.
Unfortunately, I don't have an answer for this at the moment.
There may be some changes in the way WMI interfaces with the new O/S and SQL versions that are breaking the scripts.
Incidentally, we have also upgraded to Windows 2008 R2, and we are still getting the blocking alerts.
However, we have only upgraded one SQL instance to SQL 2008 R2 as well as Windows 2008 R2, and we may be having the same issue as you.
So the issue may be with SQL 2008 R2.
If I come up with something new on this, I will post it here.
Parenthetically, see this link for a memory-leak issue with WMI and Windows 2008 R2:
http://support.microsoft.com/kb/977357
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]