>Has anybody experience of this type of overhead and perhaps
>got a list of guidelines on code to be avoided, for
>performance reasons, in DB2 SQL stored procedures
I found the following article on SQL stored procedures at DB2 Developer
Domain to be quite helpful:
http://www7b.software.ibm.com/dmdd/library/techarticle/0306arocena/0306arocena.html
Good Luck,
Fred Sobotka
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc