Passing around a SqlConnection

Question

I have created a TransactionScope and within the scope various items are created and updated in the database. During this process I make a lot of calls to the database. Original

Answer 1

In general I would agree with what others have said. Note however, that once you use multiple connections inside a single TransactionScope instance, it will promote your (local) transaction to a distributed one, thus incurring some possibly significant overhead.

Multiple connections from the same pool, thus using the same database, also count as multiple connections in this sense.

If that is an issue for you, versus code structure or "cleanness", typical SQL statement execution time, etc., you need to decide.