• @gulatimahesh: It depends on how the application manages SQL connections. CONTEXT_INFO is unique per connection.

    If the application establishes separate SQL connections for each application instance, CONTEXT_INFO will be fine in a multi-user environment.

    If connection pooling is involved, obviously by definition SQL connections could be shared between multiple instances...and in this case it would be important to understand exactly how/when the pooling assigned connections.

    Also, with connection pooling, there have been some reports that sp_reset_connection does not clear CONTEXT_INFO...though some suggest that was fixed in SQL 2005. (In other words, be careful that when you obtain a connection from the pool that you don't accidently use CONTEXT_INFO that was set by a previous connection.)