StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I tend to avoid stored procedures. The debugging tools tend to be more primitive. Error reporting can be harder (vs your server's log file) and, to me at least, it just seems to add another language for no real gain.</p> <p>There are cases where it can be useful, particularly when processing large amounts of data on the server and of course for database triggers that you can't do in code.</p> <p>Other than that though, I tend to do everything in code and treat the database as a big dump of data rather than something I run code on.</p> <p>Consider <a href="http://www.codinghorror.com/blog/archives/000117.html" rel="nofollow noreferrer">Who Needs Stored Procedures, Anyways?</a>:</p> <blockquote> <p>For modern databases and real world usage scenarios, I believe a Stored Procedure architecture has serious downsides and little practical benefit. <strong>Stored Procedures should be considered database assembly language: for use in only the most performance critical situations.</strong></p> </blockquote> <p>and <a href="http://codebetter.com/blogs/jeremy.miller/archive/2006/05/25/145450.aspx" rel="nofollow noreferrer">Why I do not use Stored Procedures</a>:</p> <blockquote> <p>The absolute worst thing you can do, and it's horrifyingly common in the Microsoft development world, is to <a href="http://codebetter.com/blogs/jeremy.miller/archive/2005/06/09/129562.aspx" rel="nofollow noreferrer">split related functionality between sproc's and middle tier code</a>. Grrrrrrrr. You just make the code brittle and you increase the intellectual overhead of understanding a system.</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload