• p.s. I also want to say that when I say "developers", I'm talking about the greater populous... there are some individual developers that I'm NOT including in my rant, but they are far and few between.

    And, I forgot a very important point in my "rant" above... on that 24 hour dupe check that I rewrote to run in 15 minutes and do 50% more work? I did a little research on how long it took to develop the "bad" dupe check using "Agile" methods... it took 2 developers a week each and that didn't include acceptance testing. It only took me 20 hours from the time I started until I delivered the final UAT tested product. Not bad for an "old style DBA", huh? 😛

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