Stored Procedure

[Guest]

I read that using stored procedures in your codes can make it more efficient.
But say if I only want to do simple queries like Select Col1 From Table1
Where Col1="ABC", should I actually use a stored procedure?

 

[Steve C. Orr [MVP, MCSD]]

The short answer is yes. One reason is that it's good to be consistent
about storing all your queries in one place. Another reason is that even a
simple query can give significant performance benefits if it's called
frequently and/or under heavy load. Another reason is the security that SQL
Server provides.

At very least use ADO.NET parameter objects even if you go with plain text
sql. They will protect you from SQL Injection Attacks.

Here's more info:
http://msdn.microsoft.com/library/d...systemdatasqlclientsqlparameterclasstopic.asp

http://msdn.microsoft.com/library/d...ngparameterizedstoredprocedurevisualbasic.asp

 

[Guest]

What I'm concerned here is that if I use a DataAdapter to update a table, I
can catch the DBConcurrencyException error and use it's Row property to get
the affected row. If I use a stored procedure to update my table, how do I
know when concurrency occurs? And how do I react?

Thank you.

 

[Steve C. Orr [MVP, MCSD]]

DataAdapters can call stored procedures, so I don't see any conflict.