In Extended Events data differs in SQL_batch_completed & sql_statement_completed

Question

Hi Team,

I have extracted Extended Events data in XEL file.

I have observed one difference that

SQL_batch_completed Logic_reads value is different than SQL_ stament_completed.

Event in the batch only one SQL is present which I matched in SQL Statement Completed.

Some records Logical Reads value is greater in SQL_batch_completed and in some records the value for logical reads in SQL_ stament_completed greater.

This difference is with others as well like CPU, durations etc.

Why such a difference?

@Dan Guzman

Answer 1

The difference in Logical Reads values between SQL_batch_completed and SQL_statement_completed events in Extended Events can occur due to the way SQL Server processes batches and statements. SQL_batch_completed event is raised when a batch of Transact-SQL statements completes, whereas SQL_statement_completed event is raised when a single Transact-SQL statement completes. It is possible that a batch of statements may contain multiple individual statements that are executed separately and may have different logical reads values. Therefore, it is expected to see differences in the Logical Reads values between these two events.

References:

• Monitor Analysis Services with SQL Server Extended Events
• Advanced Viewing of Target Data from Extended Events in SQL Server
• Quickstart: Extended events in SQL Server