Stored Proceedure or SQL in a component

[prover]

Hi All,

In a component, is it better to use a stored procedure to add, update and delete records or to just type the sql statement (ex: delete from table where ...)?

Am I assuming (rightly?) that because a .dll is compiled it'll run a sql statement just as fast as a stored procedure? Is the stored procedure redundent?

 

[JohnDTampaBay]

IMHO, a stored procedure is the better way to go. If the database logic changes for any reason, only the stored procedure being called will need to be changed on the SQL Server. If the SQL statement is in the front-end code, then the application code will need to be recompiled and deployed to all desktops that currently have it. Normally it's best to keep database functionality within the database and let the front-end handle the presentation.

--Angel
-----------------------------------
Every time I lose my mind, I wonder
if it's really worth finding.