• rharderwijk (8/11/2009)


    Brad,

    I am looking at something strange here: the output of my Profiler GUI trace and a programmatic trace do not match. I created a trace in the GUI, trying to capture the occurrence of two stored procedures, so our developers can look at the variables customers put in on the website.

    I the GUI all, looked exactly as I wanted, so I stopped the trace, did an export of the trace and ran the script on the server. After some time, I stopped the trace and looked at the output. Many more events where collected now, and a lot of stored procedures where captured that I am not interested in (all captured events where of the database I traced, so that went ok).

    First thing I did was pull your book 'Mastering SQL Server Profiler' (yes, the hardcopy) from the shelf to see if I could find anything on this particular behaviour; I could not find any hints as to a possible difference in captured events using one method or the other.

    Are you familiar with this behaviour? Do you know what does (or might) be the cause of it, and what the reason is for this difference?

    I hope you can shed some light on this!

    With kind regards,

    Rick

    If both the Profiler Trace and the Server Side Trace were identically configured, and you saw different results in two different traces, the only conclusion that I know of is the load (activity) on the server was different between the two traces.

    Brad

    Brad M. McGehee
    DBA