Home Forums SQL Server 2017 SQL Server 2017 - Development Query optimizer : bad plan for simple select Reply To: Query optimizer : bad plan for simple select

  • March 25, 2020 at 12:29 pm

    #3736854

    wrote:

    Tip for when you 'walk the second range', take the stories.id from your first query (i.e. add it to the result), and then in the second query add a criteria stories.id > {prev_max}. This is more efficient than OFFSET clauses.

    This is the second post in a row of absolute gibberish (and you only have 2 posts at this point).  Either you've posted on the wrong thread  or you're fishing to setup for spam.

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