• yuvipoy (12/15/2013)


    Jeff Moden (12/15/2013)

    There's a reason why these things are called "BLOBS". Splitting fixed length, fixed field blobs is nearly trivial if you know the "record layout" but when you add VARCHAR or any other variable length datatype to the mix, it isn't going to work unless there's an embedded delimiter in the data or something that identifies the start of each field for every row.

    There are no embedded delimiter only byte size is there.

    Only byte len is the starting point of every column.

    Based on the BYTE sizeneed to split the BLOB.

    Ok... so where is that information stored and is it stored for every row so you can do variable length columns?

    Shifting gears, it would really be nice if you took a look at the first link under "Helpful Links" in my signature line below

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