• Cool picture that, ironically, lives up to what I think of a lot of software vendors that write T-SQL have done and still do... take a look at the printing flaw in the lower right corner of the imprint on the paper. Heh... "BUG!".

    I'm still finding that software, either custom built or shrink wrapped, ummmm.... sucks. 😉 Even MS blew it on many things in the GUI's of SQL Server 2005 (IMHO) and those same mistakes and shortcomings bled into 2008. Of course, MS isn't the only one that has this problem. People (read that as mostly "managers" and "leads") just don't know how to plan and many Developers still operate under the premise that QA will catch any faults and take the shortcut of not actually testing their own code for both "happy" and "unhappy" paths. Many Developers are still of the ilk that they've been given an assignment and they just want to get it off their proverbial plate.

    Until those attitudes change and much better planning skills are realized, a lot of software will continue to make the same sucking noises under the pressure of delivery schedule that have plagued our industry since it first started.

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