• Yet Another DBA (9/16/2014)


    It will always be an ongoing battle.

    Ask a developer to use a dll, RESTful service ... Fine no worries.

    Ask a developer to use a stored procedure and majority will look at you as if you are mad.

    The arguments I have heard:

    * I cant debug a stored procedure

    * it takes too long to write the extra code

    * I cant see whats happening.

    * What happens if I need to add a column

    Begin trans <Rant Mode>

    Welll I must not be in the majority, nor almost all the people I have ever worked around. RESTful Service No Problem! Stored procedure No Problem! Relational model love it! Denormalized model for BI even more fun. If it has code GREAT! Where is the problem!

    Can't debug a stored procedure translates to not creative enough to understand how to do it, and not knowing how to monitor state as you build. SQL is just another language with an interesting syntax. It is fun, exciting, and can really do a ton of really cool things on the big iron where your data lives.

    "It takes too long to write extra code" means that there is a lazy factor there that needs to be attended to.

    "I cannot see what happens" is really simple foolishness. There are only a very few developers today who have even a remote idea what their code does and what is hidden from them during the execution of their java, javascript, python, or .net code.

    And "What happens if I need to add a column?" is obvious. You add a column and do a little work to make the magic happen. If it changes some of your really spiffy code, so what. That spiffy code did not do the things you needed to do when the data you need is fully in place.

    Who was it that said "Just Do IT!" Well get off it and do it!

    End Trans <Rant Mode>

    Have a better day!

    M.

    Not all gray hairs are Dinosaurs!