• Eirikur Eiriksson (7/14/2015)


    Jeff Moden (7/14/2015)


    That IS a good use of XML and, now that you've brought that bit of computational agony up, it's possible that I might do the same although I'd be on a bit of a mission to save space because that's a whole lot of tag bloated/datatype bloated XML.

    Yes, I know disk space is supposedly cheap... it's actually not if you consider all the aspects of storage. For example, even if it's set off in monthly, read only partitioned file groups, the data will be duplicated at least once on disk as an online backup on another disk. Then there's the cost of rack space, floor space, cooling costs, backup costs, etc, etc. No sense in intentionally wasting space unless that's truly the best and lowest cost way.

    The SQL Server stores the XML in a very efficient binary storage format, in my experience only around 20% larger than zipped XML.

    😎

    Now that's some good info, Eirikur. I didn't know that. I check it out. Thanks.

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