What are the disadvantages of disabling Connection Pooling ?

[apexbs]

Hi ;

I have been facing problem in connection pooling for two weeks and I did search each website and forum and I noticed that this is one the most comman problem using ASP.NET with VB.NET and SQL Server 2000. I went thru my application and checked for any open connection and I ensured there is no connection leakage. I turned ON SQL Profiler only for Connections and I noticed that after closing and destroying connections, it removes from the SQL Server pool after 6 minutes. For that reason if there more than 100 connections in a pool then it breaks the website and gave time out error.

In the end, I turned OFF the connection pooling using Pooling = false in the connection string. Now, the website is working fine but I am wondering about the disadvantage of disabling Connection Pooling. One thing is clear it will slow , any other in long term.

Thanks.

 

[chiph]

1) Slow performance, as each connection must be created and authenticated from scratch each time.

2) Higher connection usage (since SQL Server is licensed per-connection, this could cost you money)

I would suggest that if you're using C# you investigate the "using" keyword to make sure your connection is being destroyed after it's no longer needed.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first