named set questions
as understand it, named set is not processed until needed.
once these processed cached use other client requests?
if there aggregations set in cube trigger the named sets processed right away cube?
i assume if named set big there loss in performance, there way hold down size of named set?
here examples of named sets i've created using calculated members. perhaps there better way of doing this?
*************** calculated members***************************
create
member currentcube.[measures].[hp plus addl billing] as aggregate([prep control hdr].[bill formats].&[19],[measures].[billed sales amount]),format_string
= "currency",visible
= 1;2nd calculated member
create
member currentcube.[measures].[prep billing] as aggregate(except([prep control hdr].[bill formats].[bill formats] ,{[prep control hdr].[bill formats].&[19],[prep control hdr].[bill formats].&[7]}),[measures].[billed sales amount]),format_string
= "currency",visible
= 1;*******************named sets************************************
create
set currentcube.[ctp customers] as filter([customer job].[title name].[title name].members,([job complete date].[calendar full],[measures].[hp plus addl billing])> 0 );create
set currentcube.[prep customers] as filter([customer job].[title name].[title name].members,([job complete date].[year].&[2005],[measures].[prep billing]) > 5000 ) ;
this one, i've used other named sets create named set.
is bad thing?
create
set currentcube.[non-prep-photo customers] as except([ctp customers],{[prep customers],[photo customers]});
as understand it, named set is not processed until needed.
once these processed cached use other client requests?
actually no - named sets processed , evaluated during mdx script execution. done once, , cached afterwards.
SQL Server > SQL Server Analysis Services
Comments
Post a Comment