DRAG DROP
You administer a SQL Server Analysis Services (SSAS) instance.
You need to capture a continuous log of detailed event and subevent durations and custom
trace events from queries executed in the SSAS instance.
Which three actions should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)
Answer: See the explanation.
Explanation:
Box 1: Write an XMLA script to log the extended events of the trace.
Box 2: Launch SQL Server Management Studio and connect to the instance.
Box 3: Execute the script.Note:
* Auditing an instance of SQL Server or a SQL Server database involves tracking and
logging events that occur on the system. The SQL Server Audit object collects a single
instance of server- or database-level actions and groups of actions to monitor. The audit is at
the SQL Server instance level. You can have multiple audits per SQL Server instance. The
Server Audit Specification object belongs to an audit. You can create one server audit
specification per audit, because both are created at the SQL Server instance scope.
* Trace events can be started and captured using SQL Server Profiler, , or can be started
from an XMLA command as SQL Server Extended Events and later analyzed.
* Extended Event tracing is enabled using a similar XMLA create object script.
Reference: Analysis Services Trace Events
Almost identical question as 31, but different answers.
Catalog.executables does not have a duration info, so, I’d say you should use Catalog.executions with catalog.execution_component_phases
that’s correct
I think we should switch the first two.
By the way in 2016 SSAS the XE wizard added:
https://technet.microsoft.com/en-us/library/gg492139.aspx
Agree with you
should be Executions view
kindly let me know answer for this question
Could also be >
Box 1: Launch SQL Server Management Studio and connect to the instance.
Box 2: Write a MDX script to query the DISCOVER_TRACES dynamic management view (DMV).
Box 3: Execute the script.
I agree with Dim
None of these answers would help us to monitor control flow tasks. Catalog.execution_component_phases is for data flow tasks only. And catalog.executions view provides duration on package level only. But catalog.executable_statistics could help us.
I agree with you Alex. But in this case the only answer which makes sense to some extent is Catalog.executions with catalog.execution_component_phases. The rest of answers is just gibberish.
I think you should use catalog.operation_message to identify the serveral control flow tasks and for comparing time of all control flow tasks use catalog.executables.
I think you don’t have anything useful in catalog.operation_message to compare the timings:
https://msdn.microsoft.com/en-us/library/ff877994.aspx
DISCOVER_TRACES: Provides information about traces that are currently active on the server.
But you need to capture a continuous log of detailed event and subevent durations and custom trace events from queries executed in the SSAS instance,
so the correct answer should be:
Box 1: Launch SQL Server Management Studio and connect to the instance.
Box 2: Write an XMLA script to log the extended events of the trace.
Box 3: Execute the script.