Home > Articles > Data > SQL Server

Recommended Practices for SQL Server Analysis Services 2005/2008 Design

Although Analysis Services 2005 and 2008 have been available for some time, performance tuning and troubleshooting documentation is still sparse. Database administration expert Baya Dewald offers recommendations for avoiding the most commonly encountered dimension/partition design pitfalls.
Like this article? We recommend

Microsoft’s SQL Server Analysis Services (MSAS) 2005 was a revolutionary release that dramatically changed how software developers and database administrators build and manage business intelligence (BI) solutions. A huge number of new features and changes introduced with this release instigated a steep learning curve even for those IT professionals who felt comfortable building cubes with previous releases of software.

MSAS 2008, on the other hand, is an evolutionary release building on the strong foundation laid by 2005 version, fixing some issues and introducing a few additional features. By now most BI folks know how to build Analysis Services cubes; however, documentation and literature for troubleshooting and performance tuning is still sparse. This article attempts to cover some gotchas that apply to large-scale MSAS implementations where both processing and querying performance is of paramount importance to the application’s success.

Tuning Analysis Services could involve many aspects, including but not limited to hardware configuration, dimension and partition design, re-engineering MDX queries and processing XMLA statements, and tweaking MSAS configuration settings. In this article, I focus on most commonly encountered design pitfalls. The article presumes that the readers are familiar with Analysis Services terms and concepts such as measures, dimensions, measure groups, cubes, and so on.

Recommended Practices for Dimensions

The following sections offer recommendations for working with dimensions.

#1: Limit the Number of Dimensions Per Measure Group and Number of Attributes Per Dimension

Although it may be tempting to build a data warehousing solution that encompasses all business data and allows examining such data from every possible angle, the “kitchen sink” approach doesn’t always work. In fact, business users who demand such flexibility often become confused if a query filters data by more than a few dimensions. The latest releases of Analysis Services allow more than one fact table and more than one measure group per cube, so each cube could easily support dozens of dimensions. However, for best performance and manageability, try to limit each measure group to fewer than 20 dimensions.

Furthermore, be sure to also limit the number attributes in each dimension to only those attributes that are necessary for analytics. Dimension tables in the relational data source may have numerous columns that may be used for transaction level reporting, or could simply be obsolete and left over from legacy implementations of the data warehouse. If you know that a given column will never be used for analytics, do not add it to the Analysis Services dimension structure. If the column will be seldom used, be sure to set AttributeHierarchyOptimizedState property to “Not Optimized” for this attribute. MSAS will not build indexes for such attributes, thereby saving storage space and processing time.

#2: Use Dimension Properties Effectively

Each dimension has a number of properties that need to be handled with care. For large dimensions that expose millions of rows and have a large number of attributes, pay particular attention to the ProcessingGroup property. By default, this property is assigned a value of ByAttribute. During processing, Analysis Services issues a separate SELECT DISTINCT … query for each dimension attribute. Running multiple expensive SELECT DISTINCT queries could place a significant load on the relational database engine and can be time-consuming. If you change the ProcessingGroup property to ByTable, MSAS will only execute a single query without the DISTINCT keyword to populate the dimension structure.

Note that the ByTable option may use more memory on the Analysis Services host compared to ByAttribute; nevertheless, if processing performance is important and you have plenty of memory (as you should for large-scale implementations), be sure to experiment with this property to see which value works best for you. Unfortunately, there is no hard and fast rule.

#3: Use Regular Dimension Relationship Whenever Possible

Latest versions of MSAS give us the flexibility of using referenced, many-to-many, fact, and other types of relationships between fact and dimension tables. However, this does not mean that star and snowflake schemas are obsolete or that you should be building a data warehouse using the third normal form. Clearly if you don’t manage the relational data source and don’t have the flexibility of building a star schema, then you may have no option but to use the data warehouse in its current shape. However, if you care about performance, try to stick with a regular relationship whereby fact tables have foreign keys to each dimension table’s primary key. If you must use a referenced relationship (snowflake schema), then be sure to check the Materialize check box in the Dimension Relationship dialog. By doing so, you advise Analysis Services to build additional indexes for resolving the relationship/join from fact table to referenced (intermediate) dimension table to the primary dimension table. MSAS would have to join partition records to referenced dimension dynamically during query execution for un-materialized dimensions.

Fact dimensions (sometimes referred to as degenerate dimensions) have a valid business use. For example, we often need to expose invoice numbers or customer identifiers on reports. I suggest you test performance of such reports with Analysis Services and compare to the same report generated directly from the relational data source. Analysis Services is still best suited for its original intended purpose—aggregating and presenting summarized data—as opposed to reporting transaction-level details. For huge transaction-level reports, you may find that SQL queries will perform just as well or better than reports created with Analysis Services. See the next recommended practice for more tuning advice concerning fact-level dimensions.

Many-to-many dimensions are necessary for several common business scenarios; however, this flexibility comes with a performance penalty. Investigate the possibility of alternative implementation without using many-to-many relationships. If you have to use a many-to-many relationship, be sure to read and follow optimization guidelines in this Microsoft article.

#4: Use Integer Data Type for Attribute Keys If at All Possible

For best processing performance, try to use the smallest data type for attribute key columns. Although you could use string data types for key columns, they do not perform nearly as well as the numeric data types.

At times you may need to use multiple columns for the composite key for a dimension attribute. Although this practice is almost always acceptable, for large dimensions (and particularly for fact level dimensions) you may have to add an alternate key to the dimension table to ensure processing is efficient. For example, let’s suppose you have a fact level “transaction” attribute and you use company identifier, effective date, and journal entry identifier string columns as keys for this attribute. While processing this dimension, MSAS must retrieve a unique combination of three string columns, which can be very time-consuming for a dimension that contains millions of records. Instead, you can add an identity column (or another integer column uniquely identifying each transaction) to the dimension table and use it as the attribute key. Reading a single integer column will be considerably faster than reading three string columns. Storing integer keys will also be much more efficient.

#5: Use Natural Hierarchies When Possible

I trust that you have already heard this piece of advice because it has been heavily stressed in a number of white papers and presentations. Sadly, there are still developers out there who do not follow this rule, so it makes sense to repeat it here. Each dimension can have three types of hierarchies:

  • Attribute hierarchies, which expose a single attribute—for example, product price
  • User hierarchies, which group multiple unrelated attributes—for example, product category → product color
  • Natural hierarchies, where each attribute is related either directly or indirectly to all other attributes in the same hierarchy, as in product category → product subcategory → product name

Defining attribute relationships helps with both processing and querying performance, particularly when users drill down from the top to the intermediate level, and then to the lower level of the hierarchy. As a rule of thumb, you should have at least one natural hierarchy in every dimension that does not include parent-child relationships. Parent-child dimensions expose self-referencing relationships, such as employee-manager, and normally do not require any additional hierarchies.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020