I am finding that if I call to a stored procedure returning a cursor that contains 14 columns (of which none are blobs/clobs) it is taking around 40 + mins to execute, but if I use ODP.net it executes in a little over 1 min.
I have executed the SQL in SQL Developer and it takes around 40 to 60 seconds to return all the data.
Is there a setting I need to change to get the Devart dll to perform better?
Code samples can be provided via email.
Thank you,
Shawn
Davart execution slow where ODP.net has no issues
Could you please send us via our contact form a small test project with the corresponding DDL/DML script so that we can reproduce the performance issue in our environment? We will investigate it and notify you about the results.
Please try the following:
1) use ALL_ROWS instead of FIRST_ROWS_1 in the alter session statement;
2) localize the line of code which takes a lot of time to execute (it can be cmd.ExecuteReader(), reader.GetXXX(), etc).
If this doesn't help, please send us the DDL/DML script to fill your schema (or code which will fill it) so that we can reproduce the timing issue in our environment.
1) use ALL_ROWS instead of FIRST_ROWS_1 in the alter session statement;
2) localize the line of code which takes a lot of time to execute (it can be cmd.ExecuteReader(), reader.GetXXX(), etc).
If this doesn't help, please send us the DDL/DML script to fill your schema (or code which will fill it) so that we can reproduce the timing issue in our environment.