Skip to Content
Former Member
Sep 23, 2016 at 08:32 AM

ADO not releasing objects on Connection close


After moving to Sybase 16 ADO drivers, we've found some programs using up a few Gig of space (much more than in then previous version)

We tracked this down to a stored proc being executed but all the result sets not being read.

However, this problem didn't manifest itself in earlier versions of ADO.

From what we can tell comparing running the old and new drivers, when the Connection Pool is being used the Disposing of objects is done when a connection is re-used and not when it is closed an released back the pool. (Close no longer setting the NeedToDispose flag ?)

Have we diagnosed this behaviour correctly ?

Is this expected or desirable behaviour ? If so, why ?

Should we be altering our code to allow objects to be disposed of ?