SQL Server Audit Output Generates Huge Readings

Question

I use the SQL Server Profiler to determine which process is using the SQL process, and I find that the Audit Logout event class causes a huge amount of reads and consumes the processor.

This is normal? Or is there something wrong with my SQL Server configuration?

Answer 1

An audit completion event aggregates many of its values, such as read / write, connection time, etc. since opening the connection.

See http://msdn.microsoft.com/en-us/library/ms175827.aspx - a definition for your specific question is added here:

Reads Number of logical read I/Os issued by the user during the connection.

Basically, the number you see is not for the audit event itself, it is for all actions performed by a disconnected connection.