I think the flood of replies disagreeing with you suggest you might want to rethink that assumption. Another reply to your post said you are making a 'religiou

I think the flood of replies disagreeing with you suggest you might want to rethink that assumption. Another reply to your post said you are making a 'religious argument' - I think there is some truth in that. If you had said "in my experience, shared procs are not a good place to store business logic", that would have been your opinion, and no-one could argue with you. But you stated, as fact, that "business logic should be written in code, not in data and not in the database". This is not objectively true for all companies, and can be easily disproved. And was disproved, by all the people who said this assumption is incorrect. Throwing around the names of authors does nothing to help your case (useless "appeal to authority"). I have read some of Robert Martin's work (but none of Martin Fowler's) and still think storing business logic in database rules can be a very good idea.