Great rant on one of my favorite topics as well. SQL is not for all your business rules. :) Can I ask a stupid, rhetorical question? Why do we continue to put business logic inside of SQL Procs? Can anyone answer me this? About the only half way decent answer I have ever heard is: Because we have some of this type of logic (Business Logic/Rules) inside of a sql proc we are able to update/change/modify this rule on the fly without the need to redeploy assemblies. I am sorry, but this is about as lame of a reason to do something as I have ever read/heard. Yes, I will admit that when you do put logic into your procs you do not need to redeploy. However, you are making this decision at the expense of other, better decisions. When you put your logic inside your procs you are doing many, many things which I believe are bad.