Performance Impact of Constant Login / Logout SQL On High Latency Connection I'm reviewing the performance of a .NET application that sends 1,000s of consecutive select statements to a Microsoft SQL Server 2014 Instance. Ping time to server from client is 70 ms or higher across a WAN.

The client application is using Ole DB to connect to the SQL database.

Almost every single query SQL Profiler shows this pattern


Audit:Login
SQL:BatchStarting (Single SELECT statement)
SQL:BatchCompleted
Audit:Logout
RPC:Completed - exec sp_reset_connection


This repeats thousands of times. Is it possible the application could be re-coded to avoid constant login / logout, saving expensive network calls

Or is it expected to see this information for every query.
If Audit:Login EventSubclass=2, then this is expected, and shouldn't be an issue.  The client is just reusing a connection from a connection pool and "resetting" the connection to clear any impersonations, temp tables, session settings, etc.