• dave.clark (1/27/2011)


    Thanks for the excellent info!

    I tackled this issue myself previously, but my solution is not quite as "simple" 😉

    I'll have to test this and see if I can replace my lengthy solution.

    Hi Dave,

    Thanks for the great feedback.

    Before you replace your "lengthy solution", remember that this bit of "SQL Spackle" doesn't care where a "split" occurs and will frequently split the rows right in the middle of a word and may even produce an extra blank row if the number of characters is evenly divisible by 8000. My method is just a "Quick'n'Dirty" way of verifying what's in a column that's too long to see using a simple SELECT.

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