Search
InstantDoc ID
GO

Browse By: Author | Issue

June 22, 2006 04:22 PM

SQL Server Profiler: 2005 vs. 2000

Rating: (0)
Brian Moran
SQL Server Magazine
InstantDoc ID #50260
As I explained in "Duration and CPU Values" SQL Server Profiler captures duration times in microseconds and milliseconds. How you work with Profiler is different in SQL Server 2005 and 2000. Profiler aficionados know that Profiler running under SQL Server 2000 never shows a duration value that's between 1ms and 9ms, but you might see a 0 or a 10 and higher (for an explanation of why, see "Granular Timing Statistics From Profiler," August 2005, InstantDoc ID 46889). In contrast, Profiler runnin...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Compare Member Benefits

Add a Comment

Jason,

SQL Server 2005 traces have a different set of default events, so that could explain the difference. SQL Server 2000 does not accurately capture times below 10MS, but it will capture events that show 0MS for a duration.

Hope that helps,

Brian Moran
Managing Partner; North America
Solid Quality™ Mentors

Diana7/5/2007 1:29:36 PM

Does that mean SQL 2000 omitted the rows with a duration of 10ms or less? I just did a SQL 2005 trace for 20 minutes that genarating a whopping 25 GB of trace files. In SQL 2000 I could trace the same database for 1 hour and not top 2 gb of trace files. Needless to say 90% of my rows in my SQL 2005 trace have a duration of 0. Is this granularity difference the reason for my huge trace files?

REMON4/27/2007 6:36:49 PM

You must log on before posting a comment.

Are you a new visitor? Register Here
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS

© 2010 Penton Media, Inc.

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.