ADO.NET and SQLServer Connection Pool

Question

• What it is?
• How to implement a connection pool with MS SQL?
• What are the consequences when  
  •     
  • Doing many queries one by one (i.e. using a loop with 30K + iterations invoking a stored procedure)?    
  • Performing multiple queries that take a lot of time (10 + min)?  
• Are there any recommendations?

Answer 1

A connection pool is a reuse mechanism for connections, because establishing a new connection is slow.

If you use the MSSQL and System.Data.SqlClient connection strings, then you already use it - in .Net this material is under the hood most of the time.

30k ( T-SQL), , sproc.

- , -, Asp.Net , .

Answer 2

... SqlClient, . , , , , - ( ).

Performance Monitor XP/Vista SQL, , . " .NET CLR" " ".

Answer 3

; 30 000 , , .

Answer 4

This thread has also partially answered this thread . A search would show it. Define a connection pool in which Google would respond with the first hit of this ..

That would leave only the best practices, which I think would be a good question :)

+1 to Keith Answer . He hit the nail right on the head.

Just a polite reminder from the FAQ:

You searched the Internet before asking your question, and you come we are armed with research and information about your question ... right?