Skip to content

use-sql-server-profiler-to-monitor-analysis-services.md

Latest commit

 

History

History
35 lines (29 loc) · 2.93 KB

use-sql-server-profiler-to-monitor-analysis-services.md

File metadata and controls

35 lines (29 loc) · 2.93 KB
title Use SQL Server Profiler to Monitor Analysis Services | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology analysis-services
ms.topic conceptual
helpviewer_keywords
SQL Server Profiler, Analysis Services
monitoring Analysis Services [SQL Server]
performance [Analysis Services], SQL Server Profiler
Profiler [SQL Server Profiler], Analysis Services
ms.assetid 8b77dafc-4584-4e93-8ad7-299304391bfd
author minewiskan
ms.author owend
manager craigg

Use SQL Server Profiler to Monitor Analysis Services

[!INCLUDEssSqlProfiler] tracks engine process events, such as the start of a batch or a transaction, and it captures data about those events, thus enabling you to monitor server and database activity (for example, user queries or login activity). You can capture [!INCLUDEssSqlProfiler] data to a [!INCLUDEssNoVersion] table or a file for later analysis, and you can also replay the events captured on the same or another [!INCLUDEssASnoversion] instance to see exactly what happened. You can replay events in real time or on a step-by-step basis. It is also very useful to run the trace events along with the Performance counters on the same machine. The profiler can correlate these two based on time and display them together along a single timeline. Trace events will give you more details while Performance counters give you an aggregate view. For information about how to create and run traces, see Create Profiler Traces for Replay (Analysis Services).

The following table describes the topics in this section.

In This Section

Topic Description
Introduction to Monitoring Analysis Services with SQL Server Profiler Describes how to use [!INCLUDEssSqlProfiler] to monitor an [!INCLUDEssASnoversion] instance.
Create Profiler Traces for Replay (Analysis Services) Describes the requirements for creating a trace for replay by using [!INCLUDEssSqlProfiler].
Analysis Services Trace Events Describes [!INCLUDEssASnoversion] event classes. These event classes map to actions generated by [!INCLUDEssASnoversion] and are used for trace replays.

See Also

Monitor an Analysis Services Instance