Utada P.W. SIU wrote:
Thanks~~
You should be asking how NOT to use connection pooling. In ASP, connection
pooling is used automatically, without the developer having to do a thing.
Now, mind you, there are things a developer can do to disable connection
pooling, such as:
- failure to use an explicit connection object to open recordsets or execute
commands. This syntax:
set cn=createobject("adodb.connection")
cn.open <some connection string>
set rs=createobject("adodb.recordset")
rs.Source=<some query string>
rs.ActiveConnection = cn
rs.Open
will cause a second connection, using the connection string from cn, to be
opened and used to open rs. To prevent that, you must use the Set keyword:
Set rs.ActiveConnection = cn
See
http://support.microsoft.com/?kbid=271128
- use of the OLE DB Services attribute in your connection string to disable
pooling
- failure to close and destroy connections when you are finished with them
Here is some more information:
http://msdn.microsoft.com/library/en...l/pooling2.asp http://support.microsoft.com/?scid=kb;en-us;Q176056 http://support.microsoft.com/default...b;en-us;191572 http://support.microsoft.com/default...b;en-us;324686
Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"