Hi!
We are using Telerik Data Access with an Oracle Database (11.2).
We upgraded to VS 2015 and with that we also upgraded from Telerik Data Access (OpenAccess) Version 2013.1.418.2 to the Telerik Data Access Version 2016.1.224.1. With that came 2 problems.
1. In the new Data Access there is a timeout for the duration of commands. This we could fix by setting the backend.Runtime.CommandTimeout.
2. We have a lot of data to be transfered from the DB. We Access the data using Stored Procedures. Calling such a Stored Porcedure know uses a lot more memory on the DB Server than before. With the old Data Access the memory usage gets to 2.8GB at most. Using the new Telerik Data Access the memory usage goes up to over 8GB (Oracle RDBMS Kernel Executable) and the call fails with an oracle exception.(Machine has only 8GB memory).
Any idea on problem 2? Are there perhaps any other Configuration changes we missed?
Kind regards,
Jürgen
1 Answer, 1 is accepted
glad you found the solution to problem #1.
Issue #2 is a bit more mysterious to me. I'm not aware that/how the stored proc could suddenly use more memory in the server. The only idea I have at the moment is that there is a code path or configuration that pushed the right type of parameters in the past, but now uses something else; this in turn would let the server execute with a different execution plan which then could have different memory characteristics.
I have seen such behavior in the past when by mistake a NVARCHAR column was used with a VARCHAR parameter and suddenly the defined index was no longer used....
As you are calling a stored proc, this also rules out the possibility that a different SQL was generated.
Could you perform a server side analysis to check the difference between old and new assemblies?
Regards,
Thomas
Telerik by Progress