If I can influence the decision it's stored procedures for everything and no ad-hoc SQL ever. Not even for selects.

This way I know what queries are run on my database, can do static analysis, generate and search through the execution plans without slowing down the system with tracing and running the risk of missing a vital query that runs only occasionally, make changes to the layout and hide them from the application(s), ensure the data consistency and business rules, ...

I've been pretty anal about this in my main past project and I do believe it paid off. Stored procedures and generated code.

Jenda
Enoch was right!
Enjoy the last years of Rome.

In reply to Re: How aggressive is your database leverage in application development? by Jenda
in thread How aggressive is your database leverage in application development? by metaperl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.