Post reply

Upgrade to SQL2019 from 2012 and everything is slow - what to look for?

  • December 22, 2023 at 7:13 am

    #4350632

    Brent Ozar makes good points about SQL 2019 performance issues:

    https://www.brentozar.com/archive/2023/03/is-sql-server-2019-more-cpu-intensive-than-sql-server-2016/

     

    DBASupport

  • December 22, 2023 at 7:55 am

    #4350665

    Update.  We migrated from 2016 Enterprise Edition to 2022 Enterprise Edition.  Virtually everything is run 30-40% slower.  I also did some simple tests between 2017 and 2022 on the same machine (my laptop).  The code I used requires no disk access and the output dumps to a "TrashIt variable).

    SQL Server 2022 just sucks for performance.  According to a lot of people that I shared the code with for testing, the performance suck factor was present in 2019, as well.

    All this stuff about using QUERY STORE to find problem queries is a bit of bunk to me... the code was fine in 2016 and now it's not.  There should not be a 30-40% performance penalty just because you upgraded.  And that includes the CU9 update for 2022.

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

  • January 3, 2024 at 5:13 am

    #4355928

    Some good comments from the best minds.

     

    DBASupport

Viewing 3 posts - 16 through 17 (of 17 total)

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