Subject | Good DB design: When to use stored procedures? |
---|---|
Author | Zd |
Post date | 2008-04-19T11:30:39Z |
Hi,
I've read in the FB papers that using stored procedures is highly recommended because it optimizes network traffic and makes query execution faster.
The question is:
I have over 50 tables in my DB and a lot of different queries acessing them in different ways. If I started making stored procedures for each dynamic query I'm executing now from my program, I'd end up with 200 stored procedures at least.
So is it a good idea to put EVERYTHING into stored procedures (like even a simple update or insert into statement which puts a few rows to the DB)?
Thanks:
Zd
[Non-text portions of this message have been removed]
I've read in the FB papers that using stored procedures is highly recommended because it optimizes network traffic and makes query execution faster.
The question is:
I have over 50 tables in my DB and a lot of different queries acessing them in different ways. If I started making stored procedures for each dynamic query I'm executing now from my program, I'd end up with 200 stored procedures at least.
So is it a good idea to put EVERYTHING into stored procedures (like even a simple update or insert into statement which puts a few rows to the DB)?
Thanks:
Zd
[Non-text portions of this message have been removed]