none
Best Practice for quarterly Security Patching for SQL Server: RRS feed

  • Question

  • Hi We have SQL Server following versions . how do we ensure apply latest security patches on SQL  Servers. What is office site for the different versions  

    2008 SP3 SE

    2008 SP2 SE

    2012 SP1 SE

    2014 SP1 CU4

    2014 RTM

    2016 SP1

    2016 SP2

    Please note we do apply quarterly windows server security update on all Widows server which run SQL servers . But I understand Windows patches are separate to SQL Server patches and Windows patch will not apply to SQL Server binary point.

    It’s a great help if anyone can advise on this

    Many thanks


    • Edited by ashwan Friday, September 6, 2019 2:22 AM
    Friday, September 6, 2019 2:20 AM

All replies

  • Hello Friend,

    First, back up everything.
    The website for the latest versions of Sql Server follows:

    Apply the last CU for each version and everything will be fine.

    Microsoft SQL Server Versions List

    Versions:

    Release <abbr title="Release To Manufacturing">RTM</abbr> (no <abbr title="Service Pack">SP</abbr>) Latest <abbr title="Cumulative Update">CU</abbr>
    ↓ SQL Server 2019
    SQL Server 15
    codename Aris
    Will be released
    in H2 2019
    (probably 2019/11)
    Not yet released
    ↓ SQL Server 2017
    SQL Server latest version
    SQL Server 14
    codename vNext
    Support end date: <time datetime="2022-10-11" title="October 11, 2022">2022-10-11</time>
    Ext. end date: <time datetime="2027-10-12" title="October 12, 2027">2027-10-12</time>
    14.0.1000.169 CU16 (14.0.3223.3, August 2019)
    Starting from SQL Server 2017 Service Packs will no longer be released
      SP1 SP2 SP3 SP4
    ↓ SQL Server 2016
    SQL Server 13
    Support end date: <time datetime="2021-07-13" title="July 13, 2021">2021-07-13</time>
    Ext. end date: <time datetime="2026-07-14" title="July 14, 2026">2026-07-14</time>
    13.0.1601.5 13.0.4001.0
    or 13.1.4001.0
    13.0.5026.0
    or 13.2.5026.0
    ↓ SQL Server 2014
    SQL Server 12
    Support end date: <time datetime="2019-07-09" title="July 9, 2019">2019-07-09</time>
    Ext. end date: <time datetime="2024-07-09" title="July 9, 2024">2024-07-09</time>
    12.0.2000.8 12.0.4100.1
    or 12.1.4100.1
    12.0.5000.0
    or 12.2.5000.0
    12.0.6024.0
    or 12.3.6024.0
    ↓ SQL Server 2012
    SQL Server 11
    codename Denali
    Support end date: <time datetime="2017-07-11" title="July 11, 2017">2017-07-11</time>
    Ext. end date: <time datetime="2022-07-12" title="July 12, 2022">2022-07-12</time>
    11.0.2100.60 11.0.3000.0
    or 11.1.3000.0
    11.0.5058.0
    or 11.2.5058.0
    11.0.6020.0
    or 11.3.6020.0
    11.0.7001.0
    or 11.4.7001.0
    Obsolete versions – out of support
    ↓ SQL Server 2008 R2
    SQL Server 10.5
    codename Kilimanjaro
    Support end date: <time datetime="2014-07-08" title="July 8, 2014">2014-07-08</time>
    Ext. end date: <time datetime="2019-07-09" title="July 9, 2019">2019-07-09</time>
    10.50.1600.1 10.50.2500.0
    or 10.51.2500.0
    10.50.4000.0
    or 10.52.4000.0
    10.50.6000.34
    or 10.53.6000.34
    ↓ SQL Server 2008
    SQL Server 10
    codename Katmai
    Support end date: <time datetime="2014-07-08" title="July 8, 2014">2014-07-08</time>
    Ext. end date: <time datetime="2019-07-09" title="July 9, 2019">2019-07-09</time>
    10.0.1600.22 10.0.2531.0
    or 10.1.2531.0
    10.0.4000.0
    or 10.2.4000.0
    10.0.5500.0
    or 10.3.5500.0
    10.0.6000.29
    or 10.4.6000.29
    ↓ SQL Server 2005
    SQL Server 9
    codename Yukon
    Support end date: <time datetime="2011-04-12" title="April 12, 2011">2011-04-12</time>
    Ext. end date: <time datetime="2016-04-12" title="April 12, 2016">2016-04-12</time>
    9.0.1399.06 9.0.2047 9.0.3042 9.0.4035 9.0.5000
    ↓ SQL Server 2000
    SQL Server 8
    codename Shiloh
    Support end date: <time datetime="2008-04-08" title="April 8, 2008">2008-04-08</time>
    Ext. end date: <time datetime="2013-04-09" title="April 9, 2013">2013-04-09</time>
    8.0.194 8.0.384 8.0.532 8.0.760 8.0.2039
    → SQL Server 7.0
    SQL Server 7
    codename Sphinx
    Support end date: <time datetime="2005-12-31" title="December 31, 2005">2005-12-31</time>
    Ext. end date: <time datetime="2011-01-11" title="January 11, 2011">2011-01-11</time>
    7.0.623 7.0.699 7.0.842 7.0.961 7.0.1063
    → SQL Server 6.5
    SQL Server 6.50
    codename Hydra
    Support end date: <time datetime="2002-01-01" title="January 1, 2002">2002-01-01</time>
    6.50.201 6.50.213 6.50.240 6.50.258 SP4 6.50.281
    SP5 6.50.416
    → SQL Server 6.0
    SQL Server 6
    codename SQL95
    Support end date: <time datetime="1999-03-31" title="March 31, 1999">1999-03-31</time>
    6.00.121 6.00.124 6.00.139 6.00.151


    Se esta resposta lhe ajudou, marque-a como útil para que outra pessoa com dúvida ou problema semelhante possa encontrar resposta ou ajuda mais facilmente. * Jefferson Clyton Pereira da Silva - [ MCSA | MCP | MCTS | MTA | Analista de Banco de Dados - Sql Server e Oracle ]

    Friday, September 6, 2019 2:50 AM
  • Hi ashwan

     

    Would you please refer to https://sqlserverupdates.com/?

     

     

     

    You can get the latest security pathes for each version from other updates.

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, September 9, 2019 7:19 AM