Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84650members
353991posts

[Imported] ClearSCADA OLE DB Provider Connection Pooling

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

sbeadle
Janeway Janeway
Janeway
0 Likes
0
480

[Imported] ClearSCADA OLE DB Provider Connection Pooling

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: florian, originally posted: 2018-10-24 20:07:31 Id:198
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.

--------------

**_rhenman:_**
**_We are using the ClearSCADA OLE DB provider and looking at the logs it appears that it appears that connection pooling isn't occurring._**

**_We create a new OleDbConnection object for each transaction we perform and as described here:_** **_https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ole-db-odbc-and-oracle-connection-pooling the data provider should be keeping these in a connection pool so they can be reused._**

**_Does anyone know whether the ClearSCADA OLE DB data provider supports connection pooling?_**

---------

bevanweiss:
My reading of that is the for OLE-DB, it is the .NET Framework that handles the connection pooling itself.
So this would be independent from ClearSCADA.

Are you appropriately Disposing and/or Closing the connections after you have finished with them? And how often are you Opening/Closing these connections?

Can you show the snippet of code that you're using to Open and Close/Dispose of the connections, along with the time indication of how often it's being run?

I would expect .NET to factor in a few things when it determines how it will perform connection pooling. If the latency of a Close/Open pairing isn't significant, then there is little to be gained from connection pooling (so it may opt not to use it, to keep system resource use lower), the other options will relate to security I expect, if explicit usernames / passwords are used in the connection string, then it will be impossible to really perform connection pooling, since the connection implies the user... and so you'd need to completely close the connection (and not just advise a close, whilst secretly keeping the connection open in the background... as it indicates the OLE-DB connection pooling would otherwise do).