• Lynn Pettis (3/11/2013)


    fmuzul (3/11/2013)


    Gazareth (3/11/2013)


    Well, I think you've got both ends of the argument there in the last couple of posts!

    But what's with the paranoia over DBA's Francesco? We're not all bad 🙂

    I don't think I'm paranoic over DBA's.

    I just think that sometime they overestimate the benefits of using s.p., and underestimate the problems they can give.

    The biggest problem with having the SQL code embedded in the application code comes to tuning the code. Any rewrites of the embedded code require a redeployment of the application. If the code is contained inside of a stored procedure, only the stored procedure needs to be redeployed, not the entire application.

    Maybe you live in a different world than mine. For me the redeploy of an application is not a problem, I just need to replace a .exe file, and this can happen automatically also (as many modern applications do, checking for an update somewhere into the net). Updating the code of a stored procedure could be more uncomfortable.

    And using a source version control I can know exactly who and when made a change to the application code, I can get a complete history of the changes.

    I know that version control can be applied to s.p. also, but I think this is more difficult.