Home/ Questions/Q 6997221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T20:15:23+00:00

I am tracing a bug in a library I did not write myself. When

  • 0

I am tracing a bug in a library I did not write myself. When using this library with ASP.NET, I get db connection errors because the SQLConnection seems to get closed when a second Connection is being opened with the same connection string.

Is this documented behaviour? Can opening a new SQLConnection with the same connection string close another SQLConnection object?

From debugging that seems to be the most likely cause for my problems, but I could not find anything on the web to support my theory.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No, what will happen is that when you call the SqlConnection.Open() method, even with the same connection string parameters, it will do one of two things: either reuse an unused connection from the pool, or create a new connection. Either way, you will result in non-conflicting SPIDs for SQL Server.

    • 0