I think this is more a discussion with the stand from the world you belong to.

SQL DBA vs native code writers.

Well i belong to both worlds.

I used to write VB.Net and also perform SQL DBA/developer tasks.

For me the choice wass easy.

I use the world that is the most convinient.

Most cases this was SQL Side SP.

But even when i used ad-hoc sql code in my applications, i found myself writing the statements in sql mgt studio and test them on execution performance (also Redgate sqlprompt was great help writing here;-) )

And so i have to agree with Lynn, i have found myself different times on the case that bussines logic changes so did the table structure but output in application would stay the same.

With an SP this is an easy tasks, no so in ad-hoc sql code.

With kind regards,

Van Heghe Eddy