conscious perma-coupling
-
Application startup creates a
SqlConnection
for each database it uses, and opens it, and this is then passed as a parameter from one module to the next for the lifetime of the application....to save the time opening and closing the connection.
-
Application startup creates a
SqlConnection
for each database it uses, and opens it, and this is then passed as a parameter from one module to the next for the lifetime of the application....to save the time opening and closing the connection.
-
Application startup creates a
SqlConnection
for each database it uses, and opens it, and this is then passed as a parameter from one module to the next for the lifetime of the application....to save the time opening and closing the connection.
This is actually valid in certain, rather unusual circumstances (e.g. a networked database running an old engine or configured such that it doesn't pool connections from different processes). But it's almost guaranteed that the coder just didn't know what he was doing ...
-
This is actually valid in certain, rather unusual circumstances (e.g. a networked database running an old engine or configured such that it doesn't pool connections from different processes). But it's almost guaranteed that the coder just didn't know what he was doing ...
..actually connection pooling is enabled and on (because we are using the ADO.NET client for SQL Server it is on by default and set to a pool size of 100 conenctions). The code is just not using it.
-
Application startup creates a
SqlConnection
for each database it uses, and opens it, and this is then passed as a parameter from one module to the next for the lifetime of the application....to save the time opening and closing the connection.