Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

DaveJ

(5,023 posts)
2. What about the common knowledge not to put business logic in SPs?
Wed Apr 2, 2014, 08:21 AM
Apr 2014

I've 'surveyed' the programming community (Google searched) and there seems to be a great consensus that stored procedures in an inappropriate place for business logic. I feel like it's 1999 when I'm doing that much coding in T-Sql. It's so easy to make a mistake that gets buried, there's no connection to the real world logic like there is with actual OOP objects, and for seemingly every function requires a new SP to be written, whereas with an OOP object, it can just be extended, or new objects can be added until you eventually have a machine that fits together perfectly running like a Ferrari.

Recommendations

0 members have recommended this reply (displayed in chronological order):

Latest Discussions»Retired Forums»Website, DB, & Software Developers»How do you go about creat...»Reply #2