|(New) MS released new set of Analysis Services 2005/2008 samples|
|Monday, 24 March 2008 19:14|
Microsoft just posted new set of Analysis Services 2005/2008 samples at codeplex:
Main library used by the Visual Studio for Testers to generate the MDX query load for Analysis Services server. This project was released before.
Console application to generate XML files with MDX queries to be used by the ASLoadSim library. This project was released before.
This project creates a utility that enables you to easily implement the many-to-many compression technique discussed in the Analysis Services Many-to-Many Dimensions: Query Performance Optimization Techniques best practices white paper. You can download this white paper from the SQL Server Best Practices web site at:
Reporting Services project to review the results of the simulation (logged to a SQL Server database). This project was released before.
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.
These sample scripts demonstrate how to use Powershell to query SQL Server 2008 Analysis Services DMV's. The four sample scripts enable you to cancel all queries running longer than a specified length of time, cancel a particular session/SPID/connection, retrieve the Analysis Services version, retrive a list of Analysis Services database sizes or return the results of any DMV query.
Auxilary file to be used by reporting services to define the report format
For auditing and troubleshooting purposes, you may wish to utilize a system-wide processing log file. This Codeplex project contains two XMLA scripts, CreateProcessingLog.xmla creates a system-wide processing log file and DeleteProcessingLog.xmla deletes the system-wide processing log file. You can execute these scripts either interactively using SQL Management Studio or scheduled with SQL Agent.
CreateProcessingLog.xmla defines the events and columns to be logged, for a processing log you need EventIDs 5 and 6, and then defines the columns for these events to be logged. This script logs to C:\OLAP_Processing.trc to a maximum size of 50 MB and then will automatically rollover to a new file when that size is reached.
Download this new set of samples from here.