[Advanced-ado-users] connection pooling does not work with MSSQL provider

[James L. <jl...@in...>]

I am trying to use Advanced.Data.Provider for my company's ASP.NET
portal framework. Currently, we run only on SQL Server, but we would
like to be able to support multiple databases. ADP looked perfect for
this scenario and I integrated the library with our latest development
version. However, when using ADP to connect to SQL Server 2000,
connection pooling no longer works. The site runs fine for the first few
accesses and then timeout exceptions are thrown because there are no
free connections. Using SQL Profiler, I can see connection after
connection being made to the database until the pool is used up. Has
anyone else had this problem? Does anyone know of a solution? I browsed
the source code but nothing stood out at me. Connection pooling is
supposed to be predicated on the connection string and the same
connection string should be used for all connections. If I can't get
this resolved soon, I am going to have to revert to our SQL only code
because I have a release deadline looming. Any help will be greatly
appreciated.

 

James Lacey 
Senior Software Engineer 
Interaction Information Technology 

jl...@in... 
Office: 480.889.0230 
Cell: 480.452.2435

 


CONFIDENTIALITY NOTICE: This e-mail message and its attachments are for
the sole use of the intended recipient(s) and may contain confidential
and privileged information.  If the reader of this message  is not the
intended recipient or an agent responsible for delivering it to the
intended recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, distribution, or
copying of this message is strictly prohibited.  If you have received
the e-mail in error, please notify the sender by e-mail and delete the
e-mail and any attachments.  Unintended recipient(s) are prohibited from
making any other use of this e-mail.