The information in this article applies to:
SUMMARY
OLE DB resource pooling, also known as OLE DB session pooling, is handled by the OLE DB core components. To take advantage of resource pooling, an OLE DB consumer must invoke the data provider by using either the IDataInitialize or the IDBPromptInitialize interface. (ActiveX Data Objects [ADO] attempts to do this automatically). OLE DB resource pooling can be set ON for one provider and set OFF for another. MORE INFORMATION
By default, service components are enabled for all Microsoft OLE DB providers if the provider is invoked by either IDataInitialize or IDBPromptInitialize and if the provider is marked to work with pooling by using the OLEDB_Services registry key.
In MDAC 2.0 (including all service packs) the OLEDB_SERVICES registry key under the specific provider is set to 0xfffffffc, which means that no session pooling is available. Starting with MDAC 2.1 (including all service packs) the OLEDB_SERVICES registry key is set to 0xffffffff, meaning session pooling is ON. For example, SQLOLEDB is the native OLEDB provider for SQL Server. If you install MDAC 2.0 on your computer you will see that OLEDB_SERVICES under HKEY_CLASSES_ROOT\CLSID\{0C7FF16C-38E3-11d0-97AB-00C04FC2AD98} in the registry contains 0xfffffffc. On the other hand, if you have installed MDAC 2.1 or later the same entry contains 0xffffffff. REFERENCES
For more information, see the following: Pooling in the Microsoft Data Access Components http://msdn.Microsoft.com/library/techart/pooling2.htm#pooling2_topic3 Additional query words:
Keywords : SSrvInst kbOLEDB kbSQLServ700 kbGrpMDAC kbGrpOLEDB |
Last Reviewed: October 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |