Rediger

Del via

Performance logger and callback

Download JDBC driver

Starting with version 13.4, the Microsoft JDBC Driver for SQL Server provides a performance metrics framework for tracking the timing of critical driver operations. You can use this framework to observe and analyze connection and statement execution behavior, helping identify latency bottlenecks in your application's interactions with SQL Server.

Metrics are available through two mechanisms that can be used independently or together:

  • Programmatic callback - Register a PerformanceLogCallback to receive metrics in your application code.
  • Java logging - Subscribe to dedicated java.util.logging loggers to capture metrics in log output.

Tracked activities

The driver tracks activities at two levels: connection and statement.

Connection-level activities

Activity Description
CONNECTION Total time for establishing a connection, including all subactivities.
PRELOGIN Time for TDS prelogin negotiation with the server.
LOGIN Time for the TDS login and authentication handshake.
TOKEN_ACQUISITION Time to acquire federated authentication tokens when using Microsoft Entra authentication.

Statement-level activities

Activity Description
STATEMENT_REQUEST_BUILD Client-side time to build the TDS request (parameter binding, SQL processing, packet construction). Timing-only; doesn't track exceptions.
STATEMENT_FIRST_SERVER_RESPONSE Time from sending the request to receiving the first server response. Timing-only; doesn't track exceptions.
STATEMENT_PREPARE Time for sp_prepare when prepareMethod=prepare.
STATEMENT_PREPEXEC Time for combined prepare and execute via sp_prepexec.
STATEMENT_EXECUTE Time for statement execution (sp_executesql, sp_execute, direct SQL, or batch).

Enable performance metrics

Option 1: Register a callback

Register a PerformanceLogCallback to receive performance data programmatically:

SQLServerDriver.registerPerformanceLogCallback(new PerformanceLogCallback() {
    @Override
    public void publish(PerformanceActivity activity, int connectionId,
            long durationMs, Exception exception) {
        // Connection-level metrics
        System.out.printf("Activity: %s, Connection: %d, Duration: %d ms%n",
                activity, connectionId, durationMs);
    }

    @Override
    public void publish(PerformanceActivity activity, int connectionId,
            int statementId, long durationMs, Exception exception) {
        // Statement-level metrics
        System.out.printf("Activity: %s, Connection: %d, Statement: %d, Duration: %d ms%n",
                activity, connectionId, statementId, durationMs);
    }
});

Option 2: Configure Java logging

Configure java.util.logging for the performance metrics loggers at FINE level.

In a logging.properties file:

com.microsoft.sqlserver.jdbc.PerformanceMetrics.Connection.level = FINE
com.microsoft.sqlserver.jdbc.PerformanceMetrics.Statement.level = FINE
handlers = java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level = FINE

Or programmatically:

Logger.getLogger("com.microsoft.sqlserver.jdbc.PerformanceMetrics.Connection")
      .setLevel(Level.FINE);
Logger.getLogger("com.microsoft.sqlserver.jdbc.PerformanceMetrics.Statement")
      .setLevel(Level.FINE);

Prepare method effect on statement activities

The activities tracked for PreparedStatement depend on the prepareMethod connection property. For more information about prepareMethod, see Setting the connection properties.

prepareMethod setting First execution Second execution Third+ execution
prepexec (default) STATEMENT_EXECUTE (sp_executesql) STATEMENT_PREPEXEC (sp_prepexec) STATEMENT_EXECUTE (sp_execute)
prepare STATEMENT_PREPARE + STATEMENT_EXECUTE STATEMENT_EXECUTE STATEMENT_EXECUTE
none STATEMENT_EXECUTE (direct SQL) STATEMENT_EXECUTE (direct SQL) STATEMENT_EXECUTE (direct SQL)

Note

With the default prepexec setting, the driver defers preparation assuming single use. The second execution uses sp_prepexec (combined prepare and execute). From the third execution onward, the cached handle is reused via sp_execute. To force sp_prepexec on the first call, set the connection property enablePrepareOnFirstPreparedStatementCall to true.

Sample log output

The following output shows the activities tracked across three consecutive executions of a PreparedStatement with the default prepexec setting:

ConnectionID:1, StatementID:1 Request build time, duration: 8ms
ConnectionID:1, StatementID:1 First server response, duration: 17ms
ConnectionID:1, StatementID:1 Statement execute, duration: 75ms        ← 1st call: sp_executesql
ConnectionID:1, StatementID:1 Request build time, duration: 9ms
ConnectionID:1, StatementID:1 First server response, duration: 0ms
ConnectionID:1, StatementID:1 Statement prepexec, duration: 0ms        ← 2nd call: sp_prepexec
ConnectionID:1, StatementID:1 Request build time, duration: 0ms
ConnectionID:1, StatementID:1 First server response, duration: 0ms
ConnectionID:1, StatementID:1 Statement execute, duration: 0ms         ← 3rd call: sp_execute

See also

Improving performance and reliability with the JDBC driver Setting the connection properties

  • Last updated on