Menu
The output from a SQL Server trace in profiler contains the columns CPU and Duration (amongst others). What units are these values in?
559
CPU is in milliseconds. In sql server 2005 and later, duration is in microseconds when saved to a file or a table, and milliseconds in the user interface. In sqlserver 2000, it is always in milliseconds.
Yes it affects performance. The best indicator would be to monitor your performance on the server before running the profiler and the performance once it's running. Running it on another server will still affect performance.
SQL Profiler CPU / duration units. 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 2000, the server reported both duration and CPU time in milliseconds.
According to the documentation (for SQL Server Profiler 2016) the default unit for the Duration column is milliseconds. Show values in Duration column in microseconds Displays the values in microseconds in the Duration data column of traces. By default, the Duration column displays values in milliseconds.
In SQL Server 2000, the server reported both duration and CPU time in milliseconds. 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.
You can configure the SQL Server Profiler date and time display format to assist in trace analysis. Using SQL Server Profiler, you can troubleshoot data by grouping traces or trace files by the Duration, CPU, Reads, or Writes data columns.
CPU is in milliseconds. In sql server 2005 and later, duration is in microseconds when saved to a file or a table, and milliseconds in the user interface. In sqlserver 2000, it is always in milliseconds. From MSDN.
User jerryhung gives a more accurate version-specific information in a comment:
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 2000, the server reported both duration and CPU time in milliseconds. 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.
133
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
