Load Ingest Data
Results 1 to 2 of 2

Thread: OLEDB/ADO Connection Pooling

  1. #1
    Costi Zaboura is offline World Wide Support Manager
    Join Date
    Aug 2006
    Posts
    300
    Rep Power
    14

    OLEDB/ADO Connection Pooling

    OLEDB/ADO access to various DataSources-Connection Pooling

    DESCRIPTION

    Can you supply any tips on working with connection Pooling and OLEDB?


    SOLUTION

    1) the SPTimeout property of Provider specifies the number of seconds a session can sit in the pool unused. The default is 60 seconds. The property can be added to the Provider's CLSID.

    For Attunity Connect, simply run the regedit utility and search for "Nav32.dll", you should click on the CLSID and see "OLEDB_SERVICES" property.


    If you want to modify the default simply right-click an add a DWORD property called "SPTimeout", see the attached screen capture.

    2) The following is taken from the OLEDB .NET Provider's documentation, which means that the pooling behavior in the OLEDB Bridge for NET depends on the OLEDB/ADO model, so the SPTimeout should be effective:



    .NET Framework Developer's Guide


    Connection Pooling for the .NET Framework Data Provider for OLE DB

    Pooling connections can significantly enhance the performance and scalability of your application. The .NET Framework Data Provider for OLE DB automatically pools connections using OLE DB session pooling. Connection string arguments can be used to enable or disable OLE DB services including pooling. For example, the following connection string will disable OLE DB session pooling and automatic transaction enlistment.
    Provider=SQLOLEDB;OLE DB Services=-4;Data Source=localhost;Integrated Security=SSPI;For more information about OLE DB session pooling or resource pooling, as well as how to disable pooling by overriding OLE DB provider service defaults, see the OLE DB Programmer's Reference in the MSDN library located at http://msdn.microsoft.com/library.
    CAUTION It is recommended that you always close the Connection when you are finished using it, in order for the connection to be returned to the pool. This can be done using either the Close or Dispose methods of the Connection object. Connections that are not explicitly closed might not be added or returned to the pool. For example, a connection that has gone out of scope but that has not been explicitly closed will only be returned to the connection pool if the maximum pool size has been reached and the connection is still valid.



    Articles:-

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmdac/html/pooling2.asp
    http://msdn2.microsoft.com/en-us/library/ms254507.aspx
    Last edited by Admin_attu; 09-27-2006 at 07:52 AM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  2. #2
    Adeeb Mass'ad is offline Support Manager
    Join Date
    Aug 2006
    Location
    Jaffa of Nazareth
    Posts
    169
    Rep Power
    13
    Here is how the registry entry for Attunity Connect should look like after adding the SPTimeout property:

    Attachment 77

    In this example it was set to 120 seconds.
    Last edited by Adeeb Mass'ad; 12-18-2006 at 07:02 AM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •