tag:blogger.com,1999:blog-4402664127960334547.post5911447681310922683..comments2024-03-24T10:38:58.256-05:00Comments on Nebraska SQL from @DBA_ANDY: Where are my 32-bit Perfmon Counters?@DBA_ANDYhttp://www.blogger.com/profile/09130139756284009675noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4402664127960334547.post-70781532819371096432014-08-25T02:08:47.910-05:002014-08-25T02:08:47.910-05:00Actually it is a known issue. When we were doing p...Actually it is a known issue. When we were doing performance testing for MSSQL 2008 which runs on win2008 servers, we faced similar issue as our driver box OS was win2003.<br /><br />Below is the feedback from MS for the issue.<br /> - Do not use Performance Monitoring tools installed on a Win 2003 server to monitor performance counters installed on a Win 2008 R2 server.<br /> - If you need to use such a monitoring environment, make sure the first connection is made from another Windows 2008 R2 server and then after that all subsequent connections from Win 2003 client machines should go through fine.<br /><br />This is the workaround we used to get over it. <br /> - mstsc to another windows 2008 server<br /> - Start collecting perfmon for SQL server2008 using win2008 server. Actually we can just add the counters and then cancel it. It is just the loading matters.<br /> - If you are not able to collect perfmon on win 2003 even after above step, start "Remote Registry" services on widnows 2008 where MSSQL server is running and try again. <br /> - Now you should be able to collect permon from windows 2003 servers.<br /><br />Hope this would also helps.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4402664127960334547.post-40726178103433517662014-05-06T09:24:28.803-05:002014-05-06T09:24:28.803-05:00Dale - my point about being unsupported was that t...Dale - my point about being unsupported was that the client was running a currently unsupported version of SQL (2005) - my issue with MS in this scenario is that to make this work I had to hack by copying in a different version's DLL (64-bit vs 32-bit) - and this would have been true even if I had run into this a couple years ago when 2005 was still supported, so being off support now doesn't impact that issue.<br /><br />Thanks for reading and for your comments!@DBA_ANDYhttps://www.blogger.com/profile/09130139756284009675noreply@blogger.comtag:blogger.com,1999:blog-4402664127960334547.post-84948946569420006682014-05-05T15:00:41.675-05:002014-05-05T15:00:41.675-05:00[Disclaimer: I do work for Microsoft, but as a DB...[Disclaimer: I do work for Microsoft, but as a DBA over in Developer Division.]<br /><br />I want to applaud the heroics you went through to get the Perfmon counters working. I know sometimes our customers task us with pretty untenable situations that we need to cope with.<br /><br />My only other comment that I have is you state up front that you know it's an un-supported scenario, but then take the SQL Server team to task for having to hack it to make it work. By definition, unsupported means it won't be guaranteed to work in that scenario. <br /><br />I've had to do similar things multiple times as well, but blaming Microsoft is like blaming the dishwasher manufacturer when your salmon doesn't come out cooked just right.<br /><br />I do agree unreservedly with your 1st and 2nd points, though. :) Thanks for a great article.Dalehttps://www.blogger.com/profile/13993270800732750301noreply@blogger.com