Using Trace to Monitor and Audit Analysis Services - Microsoft SQL Server 2008 Analysis Services - page 778

FIGURE 38.12

SQL Server Profiler shows the events for a query against the Sales cube.

In SQL Server Profiler, you see the Query Begin and Query Cube Begin events, just as you
did with your earlier query. But now you have a new event that occurs just before the
progress report events: the Get Data from Aggregation event. This event (and the
Progress Report events) indicates that the query hit an aggregation and that the server
used the aggregation in the resolution of the query.

If you look at the Text Data column of the Progress Report Begin and Progress Report
End events, you'll see Started (or Finished) reading data from the 11112111111
aggregation . That string of numbers is the name of the aggregation that the query hit.

Running a More Complex Query

Now let's try a query that is a little bit more complex:

SELECT {[Measures].[Store Sales]} ON COLUMNS,
[Product].[Product Name].members ON ROWS
FROM [Warehouse and Sales]

With this query, SQL Server Profiler shows a different face (of course). You should see what
is shown in Figure 38.13.

Just as with our other queries, SQL Server Profiler starts with the Query Cube and Query
Cube Begin events. The serialize events follow, and they feature a new event indicating
that the server had to serialize one more axis; we now have axis 0 and axis 1. If you