Re: Sql 2005 Profiler

From BOL

"In 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, 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."

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/17e821ca-a12e-4192-acc1-96765d9ae266.htm

--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com


"jvcoach23" <jvcoach23@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF7EBEE6-4B5A-4AD3-98AF-ECBCFBC716B6@xxxxxxxxxxxxxxxx
I've been doing some time test between Sql 2000 sp3a and Sql 2005.



Test Database Server = Server 1

It's a dual 1800 AMD, 2 Gig or RAM

Sql 2000 on the default instance

Sql 2005 running on another instance

Not running them both at the same time

Both have a max memory setting of 1800 Mb





I'm using a trc file to do the load testing through profiler. The trc was
created using Sql 2000 profiler going against a database I'll call Db2000.



I've done a timed test of running through the entire trc file. Sql 2000
is
just slightly slower than 2005 (I did a reindex, stats, recompile)



Ok.. here is my issue that I'm trying to figure out. When I run this trc
file through sql 2005 profiler on client Test1 hitting the database on
Server1 and recording the results to Server 2 (I'm only grabbing
statements
with a duration greater than 5), I'm getting sql statements that have a
duration of over 3 million. I run the that same sql statement in
Management
Studio and it takes 262.



So I'm trying to figure out why profiler is seeing the duration as over 3
million milliseconds. The trace file to run in total is never more than
15
minutes total.. so for 1 statement to say it's taking just over 50
minutes..
I just doesn't make sense that it's right.



Anyone seen this.





--
Shannon Ramirez
Network DBA


.

Relevant Pages

  • Re: ADO.NET query execution much slower than SQL Management Studio
    ... Stats being compiled on SQL Server ... If you are dynamically adding statements in a sproc, ... compare this to the profiler command (meaning what is actually run in the ... Duration: 440 ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: Queries Occasionally Slowing Down
    ... (select RowId from DataStore where dataStoreName ='name' and name = ... that is run, CPU, Reads, Writes, Duration. ... SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx ... When I ran profiler I just used the default settings. ...
    (comp.databases.ms-sqlserver)
Loading