We have created a web service and real time job where a single entry of a huge table is selected and afterwards enriched with data from other tables.
The first select from the huge table is not pushed down to the database as the “optimized SQL” shows and the complete table is loaded to the memory, which is quite time consuming.
Is there any option or “best practice” to force SQL pushdowns in real time jobs?
Thanks and best regards,
Michael Liermann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.