Has anyone noticed this phenominon with named sets. We have around 5 or 6 static sets in our calc script and they are causing very noticible slowdowns in calc script deployment and cube performance. Does anyone know if Microsoft has a fix for this? We are using 2008 R2 and have just installed SP2 but have not noticed any improvement. Changing them to dynamic sets will not help since they are complex and need to be static to work. Here are examples of what we are using. Taking the third set out causes the script to deploy in a second...leaving it in causes the sctript to deploy in a minute or more and causes a cube performance hit overall:
create SET currentcube.MyYears as [Date].[Year].[Year].Members;
create SET currentcube.MyAssetFAIDs as Filter([Firm].[Faid].[Faid].MEMBERS,[Measures].[Total Assets (YOE)]>0);
create SET currentcube.MyYearsWithFAAssets as
Generate(
MyYears
, Union(
{[Date].[Year].CurrentMember}
,
StrToSet("
Intersect({},
{Order(EXISTS(MyAssetFAIDs,[Date].[Year].CurrentMember),[Measures].[Total Assets (YOE)],BDESC)
as AssetFAIDSet" + Cstr(MyYears.CurrentOrdinal) + "})")
)) ;