• Eric M Russell - Saturday, October 21, 2017 7:01 PM

    What are their arguments for embedding the SQL in the application? Even if there were some marginal technical advantage, there is still issue that ownership of the SQL would then be moved from the domain of the DBA to the application developers. Is the app developer the smartest guy in the room when it comes to SQL, or are you?

    According to what I read, they only use the database as a place to store data.  They "upload" it to some cache using code totally devoid of any joins and then they let the code have its way with the data that's been cached.  I can see why they need  hundreds of servers to do such a thing.

    As for their Developers... who knows?  Maybe they have all the Developers in the world that actually know how to get the current date and time and that's why I can't find anyone. 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)