SSAS Extended Events

Eugene Polonichko shows how to use Extended Events with SQL Server Analysis Services:

Cubes require frequent monitoring since their productivity decreases quite often (slowdowns during query building, processing time increment). To find out the reason of decrease, we need to monitor our system. For this, we use SQL Server Profiler. However, Microsoft is planning to exclude this SQL tracing tool in subsequent versions. The main disadvantage of the tool is resource intensity, and it should be run on a production server carefully, since it may cause a critical system productivity loss.

Thus, Extended Events is a general event-handling system for server systems. This system supports the correlation of data from SQL Server which allows getting SQL Server state events.

If you’re already familiar with relational engine XEs, this isn’t much of a stretch.

Related Posts

Finding Database Growth Events

Arun Sirpal has an Extended Events session which tracks growth events on a database file: A quick post that is hopefully useful, I wanted a quick way to find the time, size of the database file size change and who caused it. I went down the extended events route using sqlserver.database_file_size_change event. By the way […]

Read More

SSAS HA

James Serra enumerates high availability options for SQL Server Analysis Services: If you are looking at providing high availability (HA) for SSAS, here are 3 options: Install SSAS on a Windows Server Failover Cluster (WSFC)Here’s a good article. The main issue with this option is that SSAS isn’t cluster-aware, so if windows is “OK” but […]

Read More

Categories

March 2017
MTWTFSS
« Feb Apr »
 12345
6789101112
13141516171819
20212223242526
2728293031