Hello folks, on all of our SQL Server 2008 R2 SP1 machines we are plagued with a WMI issue that is exactly what this Blog describes. However, the hotfix is applicable only to non-SP1 machines. Has anyone experienced this issue, and if so, how did you solve it?

If you mean Win 2008 R2 SP1 machines running SQL Server, you can give http://support.microsoft.com/kb/2697479 a try, that hotfix was released after SP1 and also addresses memory leaks with wmi

Thank you! However, that hotfix seems to fix an issue in Wmiapsrv.exe, not in WmiPrvSe.exe. We did try KB2547244 on two machines for testing, but are not yet sure whether it helped or not, because the results were mixed (we need to monitor it longer). Do you think that the hotfix you suggested is somehow related? Since it doesn't mention any problems in WmiPrvSe.exe...

you are right, my bad, I just checked for memory leak fixes for wmi after sp1, didnt check the actually file affected. the dll hotfixed in the kb i linked isnt loaded into wmiprvse.exe according to dependencywalker, so its unlikely it would affect your issue.

you can have a look here http://blogs.technet.com/b/yongrhee/archive/2012/04/01/links-to-post-sp1-hotfixes-for-windows-server-2008-r2-service-pack-1.aspx for hotfixes after sp1. though i dont see anything else related to wmi and memory leaks

Yes, that is how I found KB2547244 . I find it hard to believe though that no one else is experiencing this, since there really isn't anything special about our servers I'd say. They're plain vanilla 2008 R2 SP1 with SQL 2008 R2 and a SCOM 2007 R2 agent. We're certainly not doing anythink "funky" configuration wise. Maybe someone else will read this who has this issue too, or knows what WmiPrvSe memory usage would be normal to see in a configuration like this.

you can have a look here http://blogs.technet.com/b/yongrhee/archive/2012/04/01/links-to-post-sp1-hotfixes-for-windows-server-2008-r2-service-pack-1.aspx for hotfixes after sp1. though i dont see anything else related to wmi and memory leaks

Yes, that is how I found KB2547244 . I find it hard to believe though that no one else is experiencing this, since there really isn't anything special about our servers I'd say. They're plain vanilla 2008 R2 SP1 with SQL 2008 R2 and a SCOM 2007 R2 agent. We're certainly not doing anythink "funky" configuration wise. Maybe someone else will read this who has this issue too, or knows what WmiPrvSe memory usage would be normal to see in a configuration like this.

May I ask why you are marking two posts as answer that clearly, and in unequivocal terms, state that they are _not_ the answer?