You have a SQL Server 2012 database named database1.Users report that queries that usually take less than one second to execute, take more than 30 seconds to
execute.
You need to view the server resource consumption when the queries are executed.
What should you do?
To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the
correct order.
Select and Place:
Explanation:
Box 1: Start a SQL Server Profiler trace.
Box 2: Start a data collection by using Performance monitor.
Box 3: Save the SQL Profiler trace.
Box 4: Save the Performance Monitor data.
Box 5: Import the performance data into SQL Server Profiler.
Note:
* (step1, step 2) Both the Profiler trace and the Performance Monitor logs should be started and stopped at
about the same time.
* (step 3, step 4) Once you have completed capturing the data for both tools, you are ready to perform the
correlation analysis.* (step 5) How to Correlate SQL Server Profiler Data with Performance Monitor Data Correlating Performance
Monitor and Profiler data is a straightforward process that simply involves importing both sets of data into
Profiler. Start Profiler and load the trace file you want to correlate.
From the main menu of Profiler, select File | Import Performance Data,
* With SQL Server Profiler, we have the tools to identify the causes of such spikes. We can import
Performance Monitor log data and compare it directly with Profiler activity. If we see a spike in CPU utilization,
we can identify which statement or statements were running at the same time, and diagnose potential
problems.