Is it a good practice to use SQL Server stored procedures for INSERT, UPDATE, and DELETE statements?

Yes, anytime you pass a data modification request from a front-end application to SQL Server, it is a best practice to encapsulate the code in a stored procedure. Here are some of the reasons why:
  1. It is faster than using ADO methods to accomplish the same task.
  2. Network traffic can often be reduced because less code generally has to transverse the network.
  3. Often, stored procedures can be more efficient than Transact-SQL code sent to SQL Server not encapsulated in a stored procedure.
  4. It is often easier to debug and troubleshoot code in a stored procedure than when it is found mingled with code from the front-end application.
  5. It is also often much easier to write and maintain Transact-SQL code if it is in a stored procedure than when it is found mingled with code from the front-end application.



Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |