Pascal,

I agree. SPs do limit the number of characters send to the SQL server (except for INSERTS), but that hardly is an issue anymore, even over the internet. Over the internet the network latency is a much bigger problem, so any strategy to keep the number of roundtrips down would have a much better result. I can't see how SP vs SPT would help in that case.

In real life, as you mentioned, bad programming habbits and little understanding of writing efficient SQL is much, much more of a problem.



>The (MS)books say : stored procedures, because of bandwith and server resources usage (see the article mentioned by Mike Cole).
>
>I believe that using sp's for a simple INSERT (or basic SQL) is much overhead for little gain. For more complex queries or actions it might be a good idea to use sp's.
>
>But the most important is : often bandwith and server resources are spoiled using other "bad" habbits, that the gain of using sp's is nothing compared to the loss by those bad habbits ...