| OLAP Design Best Practices for Analysis Services 2005 |
| Written by Matt Carroll | |
| Saturday, 19 May 2007 19:55 | |
|
This paper outlines the recommended best practices for designing OLAP databases in Microsoft SQL Server 2005 Analysis Services to better meet the functional and performance needs of users. Designing a database for Online Analytical Processing (OLAP) databases is very different from designing a database for Online Transaction Processing (OLTP) and requires a different approach for achieving optimal results. The best practices recommendations are grouped into the following sections:
Within each section, these best practices are ordered roughly by priority, where priority is a combination of how important the best practice is and how often you must worry about it. Major topics not covered include best practices for the design of calculations and for server management and operations. These two topics are sufficiently complex to deserve separate and more in-depth treatment. |
Top Rated
- Why Local Cube Creation with ASSL is Superior to Local Cube Creation with the Create Global Cube Com
- Identifying and Resolving MDX Query Performance Bottlenecks in SQL Server 2005 Analysis Services
- MS Paper: 2007 Microsoft Office System Business Intelligence Integration with SQL Server 2005
- MS Document: Designing SQL Server 2005 Analysis Services Cubes for Excel 2007 PivotTables
- Configuring HTTP Access to SQL Server 2005 Analysis Services on Microsoft Windows XP
- Analysis Services Many-to-Many Dimensions: Query Performance Optimization Techniques
- Functionality & Performance Testing Analysis Services 2005 with Teradata v12
- Analysis Services Distinct Count Optimization
OLAP Design Best Practices for Analysis Services 2005
