SSAS Tools Methodology for Monitoring 2005/2008 SSAS Using Profiler trace files
Methodology for Monitoring 2005/2008 SSAS Using Profiler trace files
User Rating: / 0
PoorBest 
Tuesday, 25 March 2008 19:42

From documentation: This document explains how to set up the following components to analyze SQL Server 2005 or SQL Server 2008 Profiler trace files to locate queries and processing jobs with performance issues and to begin to understand the source of these performance problems.

  • Trace definition file. There is a SQL Server 2005 and a SQL Server 2008 CTP6 version of this template.
  • SQL Server management data warehouse for storing trace data from multiple servers, databases, and cubes into a central location
  • A Transact-SQL script for copying data from an existing trace table (either an active table or an archived table) into the SQL Server management data warehouse
  • SQL Server Integration Services packages and csv files for populating the EventClass and EventSubclass tables with data to assist in interpreting the trace files. Currently, there are only packages for SQL Server 2008 CTP6.
  • SQL Server Integration Services packages for processing the trace data from multiple servers, databases, and cubes into tables for additional analysis. There are SQL Server 2005 and SQL Server 2008 CTP6 versions of these packages.
  • Reporting Services Reports for analyzing MDX query and processing performance. Currently, there are only reports for SQL Server 2008 CTP6. SQL Server 2005 reports will be added in the next few weeks.

Methodology set (Trace definition, SQL Scrips, SSIS packages, SSRS reports) is part of Microsoft SQL Server Community Samples: Analysis Services project at codeplex.

You can read more about this utility and download it from here.