You are troubleshooting query performance on SQL Server 2008. You have profiler trace data in a table named PerfData. You need to determine which events are taking longer than one second of CPU time…

The correct answer is B. SELECT TextData, Duration, CPU. Beginning with SQL Server 2005, the server reports the duration of an event in microseconds (one millionth, or 10-6, of a second) and the amount of CPU time used by the event in milliseconds (one thousandth, or 10-3, of a second). In SQL Server 2005 and later, the SQL Server…

Troubleshoot and Optimize Databases

Question

You are troubleshooting query performance on SQL Server 2008. You have profiler trace data in a table named PerfData. You need to determine which events are taking longer than one second of CPU time or run for more than two seconds. Which Transact-SQL statement should you use?

Options

ASELECT TextData, Duration, CPU
BSELECT TextData, Duration, CPU
CSELECT TextData, Duration, CPU
DSELECT TextData, Duration, CPU

How the community answered

(40 responses)

A
15% (6)
B
75% (30)
C
8% (3)
D
3% (1)

Explanation

Beginning with SQL Server 2005, the server reports the duration of an event in microseconds (one millionth, or 10-6, of a second) and the amount of CPU time used by the event in milliseconds (one thousandth, or 10-3, of a second). In SQL Server 2005 and later, the SQL Server Profiler graphical user interface displays the Duration column in milliseconds by default, but when a trace is saved to either a file or a database table, the Duration column value is written in microseconds.

Topics

#query performance#profiler trace data#CPU time filter#duration threshold

Community Discussion

No community discussion yet for this question.

Full 70-433 Practice