I agree with Stephen too.  I also agree with you.

GOTO's served a purpose for a time but got misused and the misuse was what was actually bad.  Same thing for religion and guns.  Pizza and beer for that matter.  Anything can be misused and it is that misuse that is bad.

Then you people who elevate things to the level of religion (Object Oriented Programming, Non-dynamic SQL, Oracle, C++, etc.) and treat the rest of us like errent dogs.  We get told "Bad, bad." and swatted on the nose with a rolled up paper.  Usually it's a "white paper" that they are trying to get paid for writing.  Tisk, tisk, tisk.  How sad.

Store procedures are fine things.  SQL server implements them well.  The jury is still out on CLR integration in 2005.  As for VB, don't get me started.  I admit that I love it but nothing lower than VB-6.  Any project that gets re-written or major upgrade gets converted to 2005 instantly.  We write handheld apps, desktop apps, and services in VB 2005.  All high performance.  The key is "don't use the slow objects" unless nothing else will work.

Just like anything can be misused that same thing can also be used well.  Know the good and the bad.  Know when something is good or bad in the particlular circumstances and then use something that you are paid for.  Your own good judgement.