• Phil Factor (3/6/2011)


    Maybe we should turn it around and list all the things that they spend way too much time and effort on, Jeff.

    Good idea, Phil, except that list would be too long for a single thread. 😛 I'll just stick with they're not spending enough time on T-SQL...

    We still have to use the Quirky Update to do certain previous row calculations. We still have to make a trip to DOS or some other trickery to export. We still have to resort to Tally Table logic to do splits and use FOR XML PATH to concatenate. We still have to use recursive CTE's or While Loop logic to build a simply hierarchical path. And we still can't skip header rows that are different than the body for BULK INSERT without some data loss. We still have to shift to another type of window to select more than one table for deletion. They went backwards on the Query Designer... you can get back to your original SSMS window without closing the designer. AND, there's still no straight forward method to print Query Designer diagrams. There's still no supported method for listing files in a directory never mind finding out their creation date, modification date, or size and there's still nothing to rename them or move them once they've been processed. Heh... and none of that even starts on SMO.

    I could go on for an hour or two but that's a start. 😛

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