Database Reference
In-Depth Information
The events chosen in a profiling session are in fact classes of events. For each class,
there are many actual events that can be generated, and these are shown in the
EventSubClass
column in Profiler:
Looking at these events in Profiler itself is not particularly easy, and so saving trace
data to a SQL Server table is a good idea since it allows us to query and report on it
much more easily. We can save a captured trace session by using the
File
|
Save As
|
Trace Table...
menu or we can choose to save a trace session in advance by using
the
Save to table
option in the
Trace Properties
dialog box that is shown when we
define a new trace session.
The trace events that we are interested in are listed next. Note that event classes and
subclasses are identified by an integer value when saved in SQL Server log tables;
we provide these integer values in parentheses after the events in the following
list and there is a script to insert all these IDs into SQL Server tables available at
http://tinyurl.com/SsasTraceIDs
.
•
Command Begin
(
15
)/
Command End
(
16
): This contains only one interesting
subclass event:
°
Batch
(
12
) contains the XMLA command sent to Analysis Services to
process one or more objects.
Search WWH ::
Custom Search