Post reply

Tables with a SPARSE Column and Consumption

  • September 12, 2025 at 12:00 am

    #4634980

    Comments posted to this topic are about the item Tables with a SPARSE Column and Consumption

  • September 13, 2025 at 12:10 am

    #4650911

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • September 15, 2025 at 6:19 pm

    #4652322

    Great question.  Proof that extra features always come at a price. 😀

    It also means more page splits than normal due to "ExpAnsive" UPDATEs because of the typical extra 4 bytes per non-NULL values added and that really bad for skinny typically non-clustered indexes because of how many rows per page they store and the log file entries required to move (very roughly) half the rows to a new page.

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

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply