Abstract: A trace header with an activity identifier is sent between a client and a database server as part of a request message stream. The activity identifier gets logged by client-side connection-related traces, by server-side traces, and by database engine traces. The activity identifier can be used to exactly correlate a thread on the client to threads on the server. Additionally, specific threads within a database engine may be correlated using the activity identifier to track the threads that processed a particular request. This enhances troubleshooting of the database system, particularly when there are many concurrent users and threads.

Abstract: A trace identifier is sent between a database client and a database server using a pre-login data package along with pre-login connection open requests through the TDS protocol. The trace identifier gets logged by client-side connection-related traces, by server-side traces, and by database engine traces. The trace identifier can be used to exactly correlate a physical connection on the client to a physical connection on the server. This enhances troubleshooting of the database system, particularly when there are many concurrent users and threads.