The new ".currentmember" behavior with subselect in SSAS 2005 sp2
SSAS 2005, we normally do not need to explicitly setting .currentmember for a hierarchy because it is implicitly set by the engine. However, in sp2, explicitly implicitly specifying .currentmember can potential returns different values (see the first screen shot below).
Test Query: The test query contains two nearly identical calculated members except the second calculated member does explicitly set the .currentmember for [Date].[Calendar] hierarchy.