SQL 2016 updates

  • Hello, so Microsoft has two Feb 2023 SQL updates listed under the same CVE.  5021128 Security update for SQL Server 2016 SP3 Azure Connect Feature Pack+GDR, and 5021129 Security update for SQL Server 2016 SP3+GDR.  I support three 2016 SQL VMs within VMWare.  Question; why two updates for 2016 SQL, as they both address the same security issues?  Thank you

  • jchendorain wrote:

    Hello, so Microsoft has two Feb 2023 SQL updates listed under the same CVE.  5021128 Security update for SQL Server 2016 SP3 Azure Connect Feature Pack+GDR, and 5021129 Security update for SQL Server 2016 SP3+GDR.  I support three 2016 SQL VMs within VMWare.  Question; why two updates for 2016 SQL, as they both address the same security issues?  Thank you

    The only people that can accurately answer that question are likely the people that work at Microsoft.

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

  • Thanks Jeff, so here is Microsofts reply:

    Hi John,

    Welcome to Q&A Forum, this is a great place to get support, answers and tips.

    Thank you for posting your query, I'll be more than glad to help you out.

    What you maybe mean ... there is an update "5021129 Security update for SQL Server 2016 SP3 GDR: February 14, 2023" and one "5021128 Security update for SQL Server 2016 SP3 Azure Connect Feature Pack: February 14, 2023".

    The first one is just for users who are on the GDR "track"... and the other on is for the rest 😉

    GDR ("I only want critical security fixes!")

    CU ("I want critical security fixes and all the other fixes!")

    13.0.6430.49 is the latest fix applied to the GDR path only, and does not include non-critical-security fixes.

    It does contain this latest security fix, but not any of the fixes in the CU path.

    I hope my answer is helpful to you,

    Bjoern Peters


    I just wonder how they slipped 5021128 in as an update to 5021129, and with prerequsite of the AZURE feature pack installation

  • Aye... thanks for the feedback.  I've been mostly left out of the update loop at work.  They've got a corporate mandate and it's the Infrastructure Group that takes care of all of this for us.

    As for slipping stuff in... it's their software, remember.  We just pay to ride on it. 😀

    --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 4 posts - 1 through 3 (of 3 total)

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