Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-03-05 : 09:00:28
|
| Vikas writes "Insert Statements With Stored ProceduresHi,Is it a good practice to use Stored procedures for Insert Statements.With Select Statements Stored Procedures do have an edge over normal SQL queries. But is thistrue for Insert, Update and delete statements also. If yes, then is it a good practice to alwaysuse SP's for every SQL job from front-end...Please advise.Thanks." |
|
|
andre
Constraint Violating Yak Guru
259 Posts |
Posted - 2002-03-05 : 09:43:06
|
| You should use stored procedures for any type of database query - including INSERT, UPDATE and DELETE statements. Stored procedures not only provide better performance because they are compiled and optimized, but also provide better security.Edited by - andre on 03/05/2002 09:52:27 |
 |
|
|
Jay99
468 Posts |
Posted - 2002-03-05 : 09:45:54
|
Additionally, it bypasses object library overhead, reduces the chatter between client and db server over the network and lets you take advantage of code reuse.Now all this holds true for versions up to SQL 2K . . . but Yukon/.NET . . . only time will tell  Jay |
|
|
|
|
|
|
Insert Statements With Stored Procedures