Stored Procedure desirable or not?

[Former Member]

Hello,

We have a scenario where we have more than 25000 rows being fetched from an external DB via JDBC. We have maxed out the query.But we need to update the tables immediatly for process flags. This is a big bear on the J2EE. Is using stored procedure the solution for this? I mean execute a stored procedure for the select and another for update? How is the resource consumption on using stored procedure? I tried reducing the poll interval too but its too risky...

Any suggesitons...

- AR

[Former Member]

Hi AR,

how about selecting each row after another. You can use the "select min" statement.

We did it in:

Regards Mario

[Former Member]

AR,

JDBC discourages use of stored procedure for the reason of portability. i.e. things might not work well if you change your Database in future. But as long as your query & the code accessing the query is optimised, tuned for performance , should not be an issue.

-- Amol