Udostępnij za pośrednictwem

Announcing the Modern Servicing Model for SQL Server

  • Artykuł

This content is no longer maintained.

Please refer to the new Tech Community article with updated information.

Comments

  • Anonymous
    September 28, 2017
    I read somewhere else that although SSRS is now a separate installer, updates will appear at the same time as SQL Server updates. SSRS Power BI Server which is SSRS + Power BI bits, will have more frequent updates. Will CUs include SSRS updates or will SSRS updates now follow the same pattern as SSMS.Thanks
    • Anonymous
      September 29, 2017
      Hi Steve, please see the last question and answer in the FAQ section.
  • Anonymous
    September 29, 2017
    Currently the CUs are not included in the Offline Update Catalog limiting their availability for organizations which use 3rd party tools such as HP - Server Automation for Patch Management. With the change in servicing model noted above is there a plan to include CU's in the offline update catalog as well?http://connect.microsoft.com/SQLServer/feedback/details/3119060/sql-server-cumulative-updates-and-the-windows-update-offline-cataloghttps://social.msdn.microsoft.com/Forums/sqlserver/en-US/5d5b581a-e780-4395-9f0a-c1e19cd55042/microsoft-offline-update-catalog?forum=sqlsetupandupgrade
    • Anonymous
      October 26, 2018
      Please see FAQ 19.
  • Anonymous
    September 29, 2017
    The comment has been removed
    • Anonymous
      September 29, 2017
      The comment has been removed
      • Anonymous
        October 06, 2017
        The comment has been removed
        • Anonymous
          October 13, 2017
          The comment has been removed
  • Anonymous
    September 30, 2017
    Will the Modern Servicing Model be adopted only for SQL Server 2017 (and later) or, “Starting with SQL Server 2017” will it be adopted for all previous versions, replacing the Incremental Servicing Model?
    • Anonymous
      October 02, 2017
      Hi,The Modern Servicing Model (MSM) only applies to SQL Server 2017 and future versions.
  • Anonymous
    October 02, 2017
    Can you confirm that the CU packing with retain the its cumulative nature? For example, If we choose to skip several CU's, say more than a years worth. Will the latest CU always upgrade directly to that build? Another, more extreme way to look at this, can I upgrade from RTM (first release) to say CU 16 (~ two years worth of updates) in a single patching session?
    • Anonymous
      October 02, 2017
      Hello,In short, yes. Please refer to the FAQ section, specifically Q3 and Q13.
  • Anonymous
    October 02, 2017
    The comment has been removed
    • Anonymous
      October 03, 2017
      Hello Peter,In short yes, if that makes sense to you. Quoting from the ISM blog post "we now recommend ongoing, proactive installation of CU’s as they become available. You should plan to install a CU with the same level of confidence you plan to install SPs (Service Packs) as they are released. This is because CU’s are certified and tested to the level of SP’s. Also, Microsoft CSS data indicates that a significant percentage of customer issues are often previously addressed in a released CU, but not applied proactively. More so, CU’s contain added value over and above hotfixes. These also may contain supportability, logging, and reliability updates enhancing the overall experience."As for reboots, assuming you are referring to Windows, a reboot is only required if certain files are locked, or have been marked for replacement on next reboot. The latter would affect you in the sense that a previous install may require a reboot before you deploy a new package.
  • Anonymous
    October 13, 2017
    Well, yes, a reboot is required if files that are being replaced are currently being used.I would expect that EXEs and DLLs and other files, which provide the functionality of SQL Server, WILL be in use while SQL Server is running. Therefore, I would guess that most CU updates would require a reboot.
    • Anonymous
      March 07, 2018
      The comment has been removed
  • Anonymous
    October 26, 2018
    For template virtual machines with "prepared" installs of SQL 2017+, is it appropriate to install CUs?
    • Anonymous
      October 26, 2018
      We continue to strongly recommend continued deployment of CUs, as they are tested to the same levels of previous SPs. CUs in SQL 2017+ also deliver feature enhancements besides fixes.