Why two connections?

[Guest]

I have built a very simple single form Application, with a sqlDataAdapter,
sqlConnection, dataSet and a Grid. As soon as I load the application and bind
the data (Fill the dataset or Open the Connection) there are two connections
from my App in SQL Server (sp_who2)

This means my App will take up two licenced connections to the Server, which
could be a problem.

Can anyone explain why this is?

Thanks

 

[Mary Chipman [MSFT]]

If it's licensing you're worried about, then don't. That's not how it
works. Many, many applications use multiple connections to SQL Server
to improve throughput. SQL Server licensing isn't per connection, it's
per CAL or per processor. See the "How to Buy" page at
http://www.microsoft.com/sql/howtobuy/default.asp for details.

--Mary

 

[Guest]

Good point, thank you.

If it's licensing you're worried about, then don't. That's not how it
works. Many, many applications use multiple connections to SQL Server
to improve throughput. SQL Server licensing isn't per connection, it's
per CAL or per processor. See the "How to Buy" page at
http://www.microsoft.com/sql/howtobuy/default.asp for details.

--Mary

 

[Sahil Malik]

SQL Server doesn't go per connection license.

This behavior is due to ConnectionPooling - SqlConnection uses, but is not
the same as an actual physical database connection.

More details here - http://shrinkster.com/2p5

- Sahil Malik
http://codebetter.com/blogs/sahil.malik/