Tabular instance perfmon counters Memory\VertiPaq *** KB always 0 - by GregGalloway

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 786054 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/1/2013 6:49:16 PM
Access Restriction Public

Description

Start a perfmon trace and choose the following counters on a server with AS2012 SP1 CU1:
* MSAS11:Memory\VertiPaq Paged KB 
* MSAS11:Memory\VertiPaq Memory-Mapped KB 
* MSAS11:Memory\VertiPaq Nonpaged KB
* MSAS11:Memory\Memory Limit VertiPaq KB

The first three always show a value of zero. The last one (and many other MSAS11 perfmon counters) do properly show values.
Sign in to post a comment.
Posted by GregGalloway on 8/5/2014 at 12:33 PM
JimJao, I confirmed this fix was in a CTP of SQL2012 SP2. (I'm not sure I've validated it's in SP2, but I assume it is.) Are you not seeing it fixed? Do you see values for other MSAS11 perfmon counters, or are you getting 0's for everything (indicating there's a permissions issue with the account you're running perfmon under)?
Posted by JimJao on 8/5/2014 at 12:24 PM
Cumulative Update 1 for SP2 is already out. I haven't seen any fix for this issue.
If there is a fix, please let me know the build number.

Thank you.
Posted by GregGalloway on 3/13/2014 at 7:56 AM
I am told this will be fixed in SP2 whenever it comes out.
Posted by ClaytonHoyt on 3/13/2014 at 7:35 AM
Arg...never mind. My query was incorrect. They are all still 0. Sorry!
Posted by ClaytonHoyt on 3/13/2014 at 7:28 AM
Has this been fixed? I'm using 11.0.3393.0 and; although Paged and NonPaged return 0 I am getting values back from Memory Mapped. The value I am getting returned is the same as the Memory Limit.
Posted by Microsoft on 8/21/2013 at 5:57 PM
Hello,

Thank you for reporting this issue. We are looking into this and have another workitem to track this issue.

Thank you,
SQL Server Analysis Services Engine Team.