Quick question:

Is the ActualConnectionString that is part of DBUtils used only in the scope/thread where it was updated?

In other words, if I set it before using it in a long-running routine, will all other objects (in other threads) use the same connection string until I reset it to string.Empty?

If so, is there a workaround for this? Do I have to switch from Self-Servicing to Adapter to get per-thread connection string control?

psandler wrote:

Quick question:

Is the ActualConnectionString that is part of DBUtils used only in the scope/thread where it was updated?

No it has appDomain scope.

In other words, if I set it before using it in a long-running routine, will all other objects (in other threads) use the same connection string until I reset it to string.Empty?

If so, is there a workaround for this? Do I have to switch from Self-Servicing to Adapter to get per-thread connection string control?

You can't do that safely. You have to use adapter if you want per thread connection strings.