You are troubleshooting query performance for a SQL Server Analysis Services (SSAS)
cube.
A user reports that a Multidimensional Expressions (MDX) query is very slow.
You need to identify the MDX query statement in a trace by using SQL Server Profiler.
Which event class should you use?
A.
Get Data From Aggregation
B.
Query Subcube
C.
Query Begin
D.
Progress Report Begin
E.
Calculate Non Empty Begin
F.
Execute MDX Script Begin
https://msdn.microsoft.com/en-us/library/ms174472.aspx
0
0
C looks to be correct here, however “query end” would be much more interesting here. As we don’t have among possible answers I would take “c”
0
0
http://searchsqlserver.techtarget.com/tip/Using-SQL-Profiler-for-Analysis-Services-2005
Query Begin and Query End events advise you of course when a particular query starts and ends. Command Begin and Command End do the same thing, except they get triggered for any XMLA command, not just MDX queries.
Execute MDX Script currentExecute MDX Script beginExecute MDX Script end
Not surprisingly, these events allow you to monitor execution of the MDX script during cube processing. As with other programming languages, the same operation can often be implemented through multiple different expressions. If you find a poorly performing query (or MDX script), you can attempt to re-write it using some other construct(s) for speed.
Resuming
Query begin – all queries including Mdx query
Command begin – XMLA queries
Mdx script – cube processing
So the correct answer here is “query begin”
0
0
To me, F
https://msdn.microsoft.com/en-us/library/ms174867.aspx#bkmk_ProgressReports
0
0