SQL Server Analysis Services allows the query and exploration of huge amounts of data by pre-aggregating information.  There are several areas in which you may be able to make performance improvements:

·         Processing the cube

·         Optimizing performance in multi-user environment

·         Balancing performance when cubes are processed concurrently with user queries

·         MDX Optimization

MDX optimization issues are frequently classed into two categories:

·         Formula Engine Issues

·         Storage Engine Issues

This paper focuses on storage engine issues for MOLAP storage.

We will walk though the steps to identify problem queries and improve query performance in the storage engine.

While this paper is based on work related to a very large Customer cube, the examples shown here are translated for the AdventureWorks Database, so you may duplicate the issues, and use this as a learning tool.

Even though some of the topics covered in this Case Study are very technical, the audience includes those who have never done performance tuning in the past.

SQL Server 2008 R2 has been out for a while now, so it’s about time for even the slow adopters to begin moving to the newer software. This is a list of the most important and compelling reasons to upgrade - from a DBA viewpoint. 

This example shows how to use the functions which relate to multi-valued parameters.

This Complete Example file demonstrates error handling in SSIS. (It accompanies an article in our articles Section:Tutorial 2 - Catching Bad Data in SSIS

SQL 2005 Reporting Services. Your report allows drilldown, but there are some sections which you do NOT want to allow drilldowns ( perhaps for security reasons.) This report Groups Adventureworks products by SubCategory. Drilldown is NOT allowed for any subcategory with an 'a' in the subcategory name. This example uses the Adventureworks 2005 Database.