RE: Stored Procedures vs. SQL Statements vs. CHAIN

-----Original Message-----
From: Brian Piotrowski [mailto:bpiotrowski@xxxxxxxxxxxxxxx]
Sent: Friday, May 05, 2006 8:17 AM
To: Midrange Systems Technical Discussion
Subject: Stored Procedures vs. SQL Statements vs. CHAIN

>Can someone tell me in terms of speed which method would be best when
>working with multiple records?  Right now my code uses a series of SQL
>statements to update several hundred records in one shot.  I'm thinking
>about moving these statements to a stored procedure instead, but I
>wanted to weigh my choices against a good old CHAIN command as well.

Brian,

SQL stored procedure is a fully functional programming language. On the system 
i5 they compile as a C program so there should be no difference in execution 
compared to sql in rpg. The performance hit you might run into is when calling 
into the stored procedure from outside the sql environment.

Disregarding the performance issues of underpowered system i5s, you would be 
wise to code in sql stored procedures vs RPG whenever there is a functional 
equivalence. ( the only thing rpg does better than sql procedures is green 
screen and calling other rpg, cl and java code modules. ) When you code sql 
procedures, both you and your code are portable to other IBM DB2 platforms. RPG 
is not.

-Steve