I need to filter a pivot table based on a 2008 SSAS cube. The filters must be on a separate worksheet from the pivot table. I've got an MDX query which returns what I'd like to see:
the simple reason is that the Excel pivot table and the Query designer from Power Pivot generate different MDX and one is faster than the other in general, SSAS cubes are not designed to deliver big amounts of data in tabular form as Power Pivot requires it
(ParallelPeriod ( [REPORTING DATE]. [MonthHierarchy]. [Reporting Year],1, [REPORTING DATE]. [MonthHierarchy].CurrentMember): [REPORTING DATE]. [MonthHierarchy].CurrentMember.lag(1), [Measures]. [Complete Orderlines %]) does not help since its just summing up the percentages and divide them by the number of periods. I need a funtion that caluates the sum of all order lines on time for the past ...
I generated OLAP report from SQL Server Analysis server using Excel. When you are using Excel to generate a report from OLAP database, excel will take care of generating the required MDX query behind the scenes. That means you don't need to hand-write MDX queries yourself. So, my question is pretty simple, i.e. Is there a way to view the MDX query that is generated automatically by excel?
I'm trying to run MDX from a SQL stored proc, the stored proc returns either SQL or MDX data dependant upon some parameters, but the output of the proc must be the same (column names) regardless of where the data comes from.
Dim_Product_Hier contains the the above mentioned product hierarchy in Parent child relationship, similarly Dim_Date_Hier. Reason being users will feed target sales for any combination of product-date hierarchy. My question is using MDX or calculated members can I achive a result set like below Department, Month, Sales Actual, Sales Target
a friend from the team offered i define the IsAggreagtable property for the year to false. i did that and the scope for the year showed correctly. still, i searched the web and i found a different solution with the freeze function in mdx. can someone please explain to me why the IsAggreagtable property also correct? why is not having an "all ...
MDX parameters return strings, and so if you're then turning a string into a member you'll then need to use the StrToMember function and as you may know, using StrToMember is a good way of killing the performance of any calculated member.
