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.
);