It is generally considered better to use a sp whenever you can, it is easier to maintain (especially if the sp is used on multiple pages), it is already complied on the sql server; so is faster and complex queries are easier to both write and see.<BR><BR>Examples could be anything from a simple select to a multiple query and update
hey how is everybody.<BR><BR>i'm developing with Access.<BR>I think people say that basically, it's easier to manipulate tables and stuff like that. <BR>but I want to go to Oracle so that i can play with the stored procedures. DO YOU GUYS THINK THAT BY UPSIZING TO ORACLE IT WILL MAKE DEVELOPMENT HARDER ?? IS IT HARDER TO ADD OR DELETE FIELDS OR ADD TABLES WITH ORACLE ? ?<BR>WHAT DO YOU GUYS THINK.<BR>
Stephen,<BR><BR>Two answers come to mind: modular design and resources.<BR><BR>MODULAR DESIGN. If you plan to use the SQL in other pages of your web site, then create it as a stored procedure and call it from each page. <BR><BR>RESOURCES. If you have a very complex/resource hungry SQL statement, then the stored procedure is the way to go since it will be precompiled before you call it eliminating the time (though it may be imperceptible) when calling it and compiling it as SQL.