SqlClient - clarify if connection pooling works fine with context propagation #3137
Description
@sincejune , @alanwest , @Kielek : Any concerns over using SET CONTEXT_INFO with connection pooling? Is there a risk of the TraceId that's propagated "contaminating" unrelated SQL queries? It's great that the instrumentation library provides support for TraceId propagation, but I'd like to have some confidence that if our applications use this, we can rely on the TraceIds associated with our SQL queries to be accurate. Any info you can provide would be appreciated. Thanks!
Originally posted by @YayBurritos in #2709 (comment)