Create Calculated Members That Are Elegant and Perform Well

It's not uncommon for MDX programmers to create an elegant calculated member, only to discover that it's so slow that it can't be used in queries against a full data set. Learn why performance problems can occur and ways to work around those problems.

MDX programmers like calculations that are elegant (i.e., a solution that is simple yet powerful and easy to maintain) and have good query performance. However, it’s not uncommon for MDX programmers to create a calculated member whose business definition and initial implementation are elegant, only to find out later that the member is so slow that it’s unusable in queries against a full data set.

The article continues at http://www.sqlmag.com/Articles/ArticleID/97790/97790.html?Ad=1