astro26
asked on
Should we use Stored procedures
I work for a medium sized company and was wondering about stored procedures.
Currently we create web apps using ColdFusion, at some point they may all be converted to Java Apps.
Should we consider using stored procedures. I do not think we will change the database (oracle 8i), but we could change our programming languages in the future.
Currently we create web apps using ColdFusion, at some point they may all be converted to Java Apps.
Should we consider using stored procedures. I do not think we will change the database (oracle 8i), but we could change our programming languages in the future.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I use parameterized sql, from what I read... it seems as if SP's give you no preformance increase over parameterized sql. I just thought that if I used sp's, then it would make it very easy to interchange programming languages. The database will always be Oracle, so I do not think that will be an issue.
Thanks all!
Thanks all!
Stored procedures are the DB objects which are stored directly in the DB engine. It is better if you want to execute a long series of sqls depending on one anothers. As kennethxu told that if you change your DB it will be difficult to migrate (as if it rearly happen)
The crunch of the talk is that convert the SQL into SPs if there is a bundle of SQLs which are dependent on each other. Otherwise it is better to create dynamically SQL string and execute it against the DB. Practically you can never convert the each and very SQLs in SPs.
Thx