[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-dcom
Subject:    Auto enlistment , connection pooling and MSDASQL
From:       Mark Billingham <mbilling () MICROSOFT ! COM>
Date:       2001-07-31 8:13:49
[Download RAW message or body]


I am using the Ole DB provider for ODBC (MSDASQL) and I wish to disable
connection pooling. This is what I have done so far:

Firstly I disabled OLE DB session pooling and auto enlistment (by
setting OLE DB Services to 0xFFFFFFFC). With this configuration auto
enlistment still occurs and ODBC connection pooling takes over (It
appears that a call to SqlSetEnvAttr is made at application startup,
this is visible in an OLDB trace).

To disable ODBC connection pooling I set CP Timeout=3D0 for the SQL ODBC
driver. In this configuration auto enlistment still seems to work. This
is puzzling. MSDN states that auto enlistment and connection pooling are
linked at the ODBC level, but disabling ODBC connection pooling does not
affect auto enlistment.

Anyone know exactly what is the link between pooling and enlistment at
the ODBC level ?.
Is it possible to configure auto enlistment independently at the ODBC
level ?

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-request@DISCUSS.MICROSOFT.COM

[prev in list] [next in list] [prev in thread] [next in thread]