none
SQL 2008 R2 SP2 release to WSUS RRS feed

  • Question

  • Hello,

    With the recent release of SQL 2008 R2 SP2 I was curious as to when Microsoft will be pushing it out to WSUS services? I've already done some testing in our environment with a manual download of it, but I was hoping to release it to my production servers for a upcoming maintenance night through the proper channels in WSUS. I haven't been able to find any further details on the average release to WSUS time-frame, so I was hoping someone here could shed some light on the matter.

    Thanks in advance,

    Tuesday, August 14, 2012 6:47 PM

Answers

All replies

  • With the recent release of SQL 2008 R2 SP2 I was curious as to when Microsoft will be pushing it out to WSUS services?

    When the SQL Server Sustained Engineering team has completed all of the requisite packaging and testing exercises, it will be available. That date is not announced, and we, in this forum, have no idea. You can compare the original release dates of previous SQL Server service packs to their WSUS release dates to get a general idea.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Tuesday, August 14, 2012 11:02 PM
    Moderator
  • Unfortunately over 3 months later and we're still waiting. Sync today and still no SQL 2008 R2 SP2.  I guess Windows 2012 is sucking all SSSE team resources...


    • Edited by LeighSat Tuesday, November 6, 2012 3:32 AM
    Tuesday, November 6, 2012 3:22 AM
  • Any update on this? SQL 2008 R2 SP2 is still not showing up in WSUS, KB2630458. SQL 2012 SP1 is even showing up and came out in November, KB2674319. I installed SP2 just from download on the dedicated SQL Servers, but I use WSUS to make sure none fall through the cracks, like on a SharePoint test server. Thanks.
    Tuesday, December 4, 2012 3:08 PM
  • Any update on this? SQL 2008 R2 SP2 is still not showing up in WSUS, KB2630458. SQL 2012 SP1 is even showing up and came out in November, KB2674319. I installed SP2 just from download on the dedicated SQL Servers, but I use WSUS to make sure none fall through the cracks, like on a SharePoint test server. Thanks.

    This is a question you need to take up with the SQL Server team. I would suggest asking in the SQL Server 2008 R2 forum.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, December 6, 2012 3:16 PM
    Moderator
  • Microsoft will *not* be releasing SQL Server 2008 R2 Service Pack 2 to Microsoft Update http://support.microsoft.com/kb/2527041

    T

    Wednesday, January 16, 2013 8:35 AM
  • Microsoft will *not* be releasing SQL Server 2008 R2 Service Pack 2 to Microsoft Update http://support.microsoft.com/kb/2527041

    Thank you for the link and confirmation, Tero.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Saturday, February 2, 2013 10:12 PM
    Moderator
  • Microsoft will *not* be releasing SQL Server 2008 R2 Service Pack 2 to Microsoft Update http://support.microsoft.com/kb/2527041

    Thank you for the link and confirmation, Tero.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Does anyone know why this is? Hopefully it's not a change in policy regarding SPs and SQL Server?
    Wednesday, March 13, 2013 10:02 AM
  • Microsoft will *not* be releasing SQL Server 2008 R2 Service Pack 2 to Microsoft Update http://support.microsoft.com/kb/2527041

    T

    The relevant text from that article:

    "Note Microsoft will not be releasing SQL Server 2008 R2 Service Pack 2 to Microsoft Update"

    Friday, May 3, 2013 7:01 PM
  • I am still confused as to why Microsoft would not include it within WSUS, a product with no EOL (unless I'm missing something).  SQL R2 SP1 is included. SQL 2012 patches are included.  What gives with this sudden missing element and drop in consistency??  There is no consolidated SQL 2008 R2 'plus' SP2 package to download to get an all in one.

    Just stating that "it will not be released to Microsoft Update" (WSUS) is not an explanation.

    Anyone care to comment (for those of us who want to use WSUS) and not direct me to the SQL forum in which ppl just direct the question back here?

    Regards, Leigh

      
    Wednesday, July 17, 2013 2:00 AM
  • I am still confused as to why Microsoft would not include it within WSUS

    Because sometimes certain updates, particularly service packs (and most notably Exchange Server Cumulative Updates and KB2734608) are not suitable for installation in unattended mode. Again, these are questions you'll need to take up with the SQL Server product group.

    Just stating that "it will not be released to Microsoft Update" (WSUS) is not an explanation.

    It's a statement of fact, and that covers the scope of the discussion as it occurs in this forum. For the answer to "Why" you need to ask the people who made that decision. The *WSUS* team does not make that decision, and most of the people here you're expecting an answer from don't even work for Microsoft, so they have no knowledge of the type you seem to be seeking.

    So, I'll say this one last time: For information about specific patches/updates to specific products, and why those patches/updates do or do not get released to WU, MU, WSUS, or the Microsoft Catalog -- the appropriate source of that information is the Product Group that owns the product.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, July 17, 2013 3:11 PM
    Moderator
  • Due to SP1 for SQL 2008 R2 will be EOS after 08.10.2013

    http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=sql*&Filter=FilterSP&spdate=12

    it would be good if MS re-thing about releasing SP2 for SQL 2008 R2 to WSUS now.

    BR

    Friday, August 16, 2013 5:36 AM
  • Due to SP1 for SQL 2008 R2 will be EOS after 08.10.2013

    http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=sql*&Filter=FilterSP&spdate=12

    it would be good if MS re-thing about releasing SP2 for SQL 2008 R2 to WSUS now.

    BR

    Good luck with that BR. Looks like Microsoft SQL development team already made their decision. Get out those flash drives and start manually patching those SQL 2008 R2 servers. :)
    • Edited by antwesor Monday, August 19, 2013 1:37 PM
    Friday, August 16, 2013 4:21 PM
  • Get out those flash drives and start manually patching those SQL 2008 R2 servers.

    that seems extreme :)

    you could always use one of the many alternate software distribution tools, even if only to push the package to the servers.
    if the payload requires manual installation/intervention/interaction anyway...


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Saturday, August 17, 2013 1:10 AM
  • Hi guys,

    So does that mean that the information published in the article is incorrect? 

    http://technet.microsoft.com/en-us/windowsserver/jj839419

    thanks,

    Michael.


    Thanks, Michael.

    Monday, October 7, 2013 12:49 AM
  • So does that mean that the information published in the article is incorrect? 

    http://technet.microsoft.com/en-us/windowsserver/jj839419

    Hi,

    at a guess, I'd say yes, that TNLib article is incorrect/outdated, perhaps because MS changed their mind about releasing via WSUS.
    This SQL team blog may be able to confirm (maybe contact the blogger) :
    http://blogs.msdn.com/b/sqlreleaseservices/


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Monday, October 7, 2013 9:26 AM
  • Hi everyone, here is the official word on this from Microsoft

    Just finished the brainstorm with our security guys and did some internal search, please refer to below details.

    Between June 21 2012 and August 14th 2012, the internal servers which sign Microsoft software were misconfigured, as a result the signatures on a significant number of internally and externally distributed software by Microsoft will expire prematurely on 01/10/2013 .  The result of the signature expiration is that software binaries will be viewed as untrusted, causing them to be invalidated by Microsoft Update, fail installation, and/or detected by 3rd party security software. This issue is not limited to Windows operating systems nor is it limited to Security Updates; it may have unexpected consequences across all products, as a full listing of affected products is still under investigation.  Depending on how the different products were signed, there are several expiration “milestones” which will occur between November 2012 and summer 2013.

    As a failsafe mitigation, Windows released a bulletin in October as  Microsoft Security Advisory (2749655) http://technet.microsoft.com/en-us/security/advisory/2749655

    This effectively catches the WinVerifyTrust API calls in the operating system and returns success to the calling program (e.g. SQL Server) if a specific faulty certificate is detected.

    What SQL Server Products were affected: One of the SQL Server components that was affected was SQL Server 2008 R2 SP2 that was released in July. For this reason, SQL Server 2008 R2 SP2 was scheduled to be released via WSUS in August but was put on hold when this issue surfaced. During the testing, Other than Untrusted Publisher errors when executing a small number of affected release packages, and CAPI2 Event Log errors on WinVerifyTrust calls, no ‘hard’ SQL Server installation or runtime failures have been identified. For this reason, we are not re-releasing SQL Server 2008 R2 SP2.

    SQL Server 2008 R2 SP2 is not being released to Windows update because it is affected by the issue described in the Microsoft Security Advisory (2749655) http://technet.microsoft.com/en-us/security/advisory/2749655. Users are required to get the update via download center. SP2 is the only update that is affected by this issue and future updates will continue to be made available via WSUS.

    In a word, honest speaking, this is a Microsoft product issue, and so I’m afraid manual installation would be the only choice. I will mark this case as non-decrement. Sincerely apologize for the inconvenience for you.


    Thanks, Michael.

    • Proposed as answer by Atamidos Thursday, October 10, 2013 10:28 PM
    Thursday, October 10, 2013 12:00 AM
  • SQL 2008 R2 SP3 is out but it won't be on WSUS either :(

    "This Service Pack will not be available on Microsoft Update."
    http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/09/26/sql-server-2008-r2-service-pack-3-has-released.aspx

    Tero

    Tuesday, September 30, 2014 1:01 PM