Author: TS70363
Posted: Sun Sep 11, 2016 7:18 pm (GMT 5.5)
This has been the design since years as this module will be used by Batch and Online.
Yes I can. But changing it to a Sub module and have SQLs within, does not answer the my problem.
I am more interested in knowing
1. How do I get rid of the qualifier from the stored procedure name before invoking it?
2. Does the poor performance of the CALL statement have any relation with the way it is invoked - i.e. Host variable and hv prefixed with a qualifier?
3. And will have many parameters in the SP cause a downgrade to the performance?
4. Will a SP that is invoked by HV rebind on every call?
_________________
TS70363
Posted: Sun Sep 11, 2016 7:18 pm (GMT 5.5)
| Quote: |
| Why do you have native SP so called through batch? |
This has been the design since years as this module will be used by Batch and Online.
| Quote: |
| Why do you not convert it to a batch sub module? |
Yes I can. But changing it to a Sub module and have SQLs within, does not answer the my problem.
I am more interested in knowing
1. How do I get rid of the qualifier from the stored procedure name before invoking it?
2. Does the poor performance of the CALL statement have any relation with the way it is invoked - i.e. Host variable and hv prefixed with a qualifier?
3. And will have many parameters in the SP cause a downgrade to the performance?
4. Will a SP that is invoked by HV rebind on every call?
_________________
TS70363