OLE DB memory overflow

[marcus_herz]

Hi

We use ADS Ver. 11.10.0.22 OLE DB provider to connect MS SQL server with ADS database. We see now that after each SQL access the memory of the OLE driver increases by about 70 kB. After a while the complete server hangs.

Has anyone an idea about a solution or any experience connecting MS-SQL with ADS

Any help is welcome as this is a vital problem.

Thanks

Marcus

[michael_loop]

Could you give some details of how you are using this connection? Are you accessing ADS from SQL Server or vice versa? Are you doing simple selects and updates, or are you performing DDL? Are you writing the data from one database to another, or only sending it to a client?

For vital issues, you should open a support incident.

Regards,

Mike Loop
Senior Support Engineer
SAP Product Support

[marcus_herz]

Hi Mike

We setup the connection within a MSSQL server to only read (select ...) periodically ADT tables from an ADD and write them into MSSQL tables.(kind of replication)

Regards

Marcus Herz

[marcus_herz]

Hi

We did some test scenarios:

1. we tried a different MS OLE DB driver just to read data from another database. No memory leak. This might indicate, that the memory leak is not on the MS side. An ADS OLE DB select * from view always consumes about 5 MB. We can see this in the taskmanager. We put 128 GB RAM in the server so it lasts for 1 week until Sunday when we restart the server to free the memory. Maybe in your test scenario you should not close the connection between two select statements to see what happens then.

2. We set up a completely new environment with ADS 12 to check if this is any help. When we have results I will let you know.

Regards

Marcus

[michael_loop]

Marcus,

We tried setting up an OLE DB connection from a Visual C# application. We didn't try writing to the MS SQL Server database, since that would be done with a different driver and not likely part of the equation. We queried the database in a loop. We tried using the default connection pooling and we tried destroying the existing connection between each query. In no case were we able to reproduce the memory leak.

If you can provide a precise set of conditions (data types involved, size of data sets, frequency, custom connection settings etc.) we can try again. However, it would probably be more effective to open a support incident.

Regards,

Mike Loop
Senior Support Engineer
SAP Product Support