By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,949 Members | 1,086 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,949 IT Pros & Developers. It's quick & easy.

Stored Procedures are good or bad?

P: n/a
Say what u feel with this interesting article at:-

http://dotnetjunkies.com/WebLog/sahi.../24/33514.aspx

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Frans is an idiot.

Bob Lehmann

"Patrick Olurotimi Ige" <ig*@iprimus.com.au> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
Say what u feel with this interesting article at:-

http://dotnetjunkies.com/WebLog/sahi.../24/33514.aspx

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Nov 19 '05 #2

P: n/a
WJ
SP is one very good method of accessing data. I use it a lot, I also use it
with MS/DAAB, another good tool. The only disadvantage that I see from using
SP is I have to prepare SP for every DB task my application handles. But,
hey, without SP, I still have to write some codes (may be more) to do what
an SP can do. With SP, you can isolate core DB logic from your application.
On top of that, I do not need to give DB access to anybody, no role needed
neither. Just give EXEC right to a group and that is all about security.
Very simple. A solution that works reliably. Never break (so far for me :));

John

"Patrick Olurotimi Ige" <ig*@iprimus.com.au> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
Say what u feel with this interesting article at:-

http://dotnetjunkies.com/WebLog/sahi.../24/33514.aspx

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Nov 19 '05 #3

P: n/a
Is fire good, or is it bad? it depends on how you use it.

SP's are great for thinning down your code. Also, I can't count the number
of times that dynamic sql has generated strange results because the
developer made a typo. Also, as annoying as it is, having to make a change
to both a stored procedure and the code that utilizes it causes exceptions
to be more visible, as opposed to having dynamic sql that, for instance, was
not updated to insert date into a new field.

However, having stored procedures that manage business logic is bad, bad,
bad, bad!
Things like calculating invoice totals, where there are multiple procing
strategies, or calculating interest on accounts (which a lot of times
introducts strange rounding errors) is best done in your business layer.

"Patrick Olurotimi Ige" <ig*@iprimus.com.au> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
Say what u feel with this interesting article at:-

http://dotnetjunkies.com/WebLog/sahi.../24/33514.aspx

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Nov 19 '05 #4

P: n/a
Why? What does what I feel have anything to do with the facts?

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"Patrick Olurotimi Ige" <ig*@iprimus.com.au> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
Say what u feel with this interesting article at:-

http://dotnetjunkies.com/WebLog/sahi.../24/33514.aspx

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.