In SentryOne (latest version) - We know 'Top SQL' - Error Code of #1 is an 'error' and #2 is an 'Abort' but what does the #-1 represent? thank you as always, Greg

Hey there Greg!  Good to hear from you again.

Without going into the gory details around how SQL Sentry collects statements and matches them up, a "-1=RequestCompleted" event occurs when we see a SQL statement start, but we never see the "End" event for whatever reason.  This is sometimes due to a long(er) running query or a high amount of data moving through the XE ring buffer.    The best way to think about it is a SQL statement that we definitely saw start, never saw it explicitly end, and artificially marked it as being closed/finished.

Hopefully this helps explain it...let us know if you have more questions about it!

-BT

Hey there Greg!  Good to hear from you again.

Without going into the gory details around how SQL Sentry collects statements and matches them up, a "-1=RequestCompleted" event occurs when we see a SQL statement start, but we never see the "End" event for whatever reason.  This is sometimes due to a long(er) running query or a high amount of data moving through the XE ring buffer.    The best way to think about it is a SQL statement that we definitely saw start, never saw it explicitly end, and artificially marked it as being closed/finished.

Hopefully this helps explain it...let us know if you have more questions about it!

-BT