I've written a simple data access layer component to call stored procs on a Oracle DB. This component is implemented as an in-process dll. I am testing some batch type applications where I am passing a shaped recordset to the data access component to insert into the DB. Unfortuneately,
the DLL(or provider) is either leaking memory or just comsumming a tremendous amount of memory. I'm using ADO 2.1,
and Oracle 8.15. Each successive call to the insert method seems to absorb about 2 to 4 K of memory and is not freeing it up. I am explcitly releasing all resource and am puzzled.
Anybody out there with similar experinces? I have tried all the providers and even ODBC connections. The batch app attempts to insert about 80,000 shaped records. Each shaped recordset contains 4 child recordsets with up to 30 records in the most populated child. Any ideas or comments would be greatly appreciated.
