Post reply

Store Procedure

  • February 23, 2017 at 7:02 pm

    #1930079

    I absolutely use a tally table, but I may use a smaller one than the sysobjects cross sysobjects one. I typically have a snippet of code that builds 1000 rows, which is often sufficient for me. However, I build the tally table, knowing the size.

  • February 23, 2017 at 7:40 pm

    #1930083

    Steve Jones - SSC Editor - Thursday, February 23, 2017 7:02 PM

    I absolutely use a tally table, but I may use a smaller one than the sysobjects cross sysobjects one. I typically have a snippet of code that builds 1000 rows, which is often sufficient for me. However, I build the tally table, knowing the size.

    Done correctly, the only time size should matter here is if it's too small.  There's no disadvantage to having it be able to "go large", which ever method you may use.

    --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 2 posts - 16 through 16 (of 16 total)

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