I think you will simply have to talk to the sender of the data about which possible fields could have this type of bottlenecks...I would expect fields like "Description" to have special c ...
Thanks for your reply. However, there're lot of places that we are using such INSERT function and each function has a lot of parameters. Is there any way that I can fix this problem without adding som ...
We have such ESQL code in our project:
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
CALL CopyMessageHeaders();
-- CALL CopyEntireMessage();
DECLARE SEQ_NO INTEGER;
DECLARE MSG_NAME CHA ...