• marcia.j.wilson (11/22/2014)


    Louis Davidson (@drsql) (11/22/2014)


    Jeff Moden (11/22/2014)


    It seemed to me to be yet another article chastising the people who are actually concerned with what the customer actually received for the sake of meeting some bloody schedule most likely agreed to by two suits in an elevator rather than with any thought as to what it would actually take.

    Wow, I really hope not, and if many other people feel that way, I will rewrite it completely. ...

    I didn't take it that way at all. I thought you made a good point.

    I've seen both scenarios:

    - The manager who has no idea what it takes to get things done and sets deadlines arbitrarily.

    - IT people who have no idea what it takes to make the business run and want things so perfect that they never get done.

    We both need to understand each other a bit better.

    I absolutely agree on the "understanding each other a bit better" thing but it presumes that the good people in IT, especially DBAs, want things to be "perfect" with no understanding of anything else on their part. My exception to this article is that nothing could be further from the truth and, despite the extremely noble intent of the author, it shines a bad light on good DBAs that actually know what being a DBA means.

    Of course, that's just my opinion.

    --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)