Stored procedures are BAD...a philosophical question

Question

Stored procedures are BAD...a philosophical question

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

GregLyon SSCommitted Points: 1946 More actions · Answer 1

Peter, I think you're right even though it was a tongue in cheek statement you made. I'm also running up against the 'We don't understand it so therefore it must be simple' attitude. That doesn't help either.

In any case, it should be an interesting meeting later this week...

Jack Corbett SSC Guru Points: 184394 More actions · Answer 2

I always favor stored procedures for data access. Even if I were using views I would not write select statements in the front end against the view, I would write an sp against the view. As far as business logic goes, if it is core to your business and proprietary you can handle that in middleware, but still use sp's for data access and let the middleware manipulate the data according to the proprietary business rules. Clearly the corporate people do not understand the power and correct use of sp's. There is a reason all enterprise level DBMS have sp's and why MySql is adding them.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

GregLyon SSCommitted Points: 1946 More actions · Answer 3

Thanks for that very strong pro SP post Jack.

I'm afraid that I'm dealing with some IT folks who either A) have Stored Procedures confused with some other feature of SQL Server, or B) have a political agenda to follow, or C) just don't know what they're talking about. Since I've been the sole developer/dba on my project for the past 3 years I was afraid I'd missed some big <ahem> paradyme shift </ahem> in SQL thinking...I'm glad to know it's just not the case.

Now I just have to figure out how to say 'you don't know what you're talking about' at the next meeting without sounding condescending...

GregLyon SSCommitted Points: 1946 More actions · Answer 4

For those of you who may have been following this thread:

Today I got to ask why stored procedures are "bad" for SQL Server applications. First off, the stance was toned down quite a bit from what it was two weeks ago. Second off, the response when I asked directly about stored procedures again was... "Well, what we meant to say is that IF it's a Web client based application (it's not) AND there are lots and lots of users (there aren't) AND you're including business logic in your stored procedures (Ok, I do some of that) THEN you should be using some middleware instead of Stored procedures to handle the business logic so as to keep the processing load off of SQL Server".

Makes perfect sense to me. Sure sounds different than the statement: 'Stored procedures hurt performance, you should be using Views' that caused me to start this whole thread...: