We have a stored procedure
sp_foo that contains dynamic sql and at the end of
sp_foo the dynamic sql is executed using
While analyzing a trace profile i noticed that the Eventsquence (ES), the start and end time do not match my expectation.
Row EC ES Start_Time End_Time D_ms SQL C 45 1293 44.240 45.603 1363 Select ... D 45 1294 43.737 45.603 1866 execute (@query) E 12 1296 43.730 45.600 1871 execute sp_foo @id=34
- Why has E the highest EventSequence (
ES=1296), is started first and finishes first?
- Why has C the latest start_time, but the lowest EventSequence (
I used this query
Select EventClass as EC, EventSequence as ES , Duration/1000 as duration_ms , convert(time, StartTime) as [Start_Time] , convert(time, EndTime) as [End_Time] .... From TraceImport WHERE EventClass in (10, 12, 45)
Update to comment on first answer
Gareth points out that my Eventsequence might be running from high to low. I believe that this is not the case yet
- my Eventsequence values are ascending (later start_time == higher ES value)
- My ES numbers are in the 2.73E7 range; According to SQL Server Planet Bigint Max Value the maximum value for an Bigint in SQL Server is 8 bytes big from:
9223372036854775807If i am not mistaken this would mean that my ES values had to be in the range of
Therefore i assume that bigint was not reached yet. We are using 2008R2 Version 10.50.4339.0