Databases
StackOverflow2013
Postsdbo
POThe Stored Procedures Feud
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POThe Stored Procedures Feud
    primarykey
    data
    text
    <blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/15142/what-are-the-pros-and-cons-to-keeping-sql-in-stored-procs-versus-code">What are the pros and cons to keeping SQL in Stored Procs versus Code</a> </p> </blockquote> <p>I was listening to <a href="http://www.hanselminutes.com/default.aspx?showID=282" rel="nofollow noreferrer">Hanselminutes podcast "Rise of The Micro ORM,"</a> where one of the guests (Sam Saffron and Rob Conery) outlined the classic reasons that DBA's insist on stored procedures:</p> <ol> <li>They are pre-compiled, which gives them an execution speed advantage</li> <li>They hide the underlying database scheme, which allows a separation of interface and implementation that prevents brittleness.</li> </ol> <p>A guest then said these aren't good arguments, and suggested the real reason the DBA's will insist on stored procs is because they simply want to protect themselves from the ignorance of the middle-tier developers.</p> <p>I found that statement to be a bit on the extreme side. Certainly I can agree that argument #2 is flawed, but I thought it was well known that sending arbitrary (uncompiled) SQL to the database was a performance hit. Is there something I'm missing that would explain why argument #1 is not really true?</p> <p>My own answer, as just a guess, is that there is a performance hit - but it rarely matters. It is perhaps analogous to a developer who attempts to optimize every loop he writes, even though only 1% of the loops written ever benefit from the tuning. Am I capturing the thought correctly?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USBrent Arias
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POThe Stored Procedures Feud
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POThe Stored Procedures Feud
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POThe Stored Procedures Feud
      1. USSly
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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