Freigeben über

Cumulative Update #2 for SQL Server 2012 SP3

  • Artikel

Dear Customers,

The 2nd cumulative update release for SQL Server 2012 SP3 is now available for download at the Microsoft Support site.

To learn more about the release or servicing model, please visit:

Comments

  • Anonymous
    March 22, 2016
    Can we get some clarity around https://support.microsoft.com/en-us/kb/3120595 ?The definition 'Assume that you edit a table that has dropped, variable-length columns in Microsoft SQL Server 2012. When you update the value of a column, the data of another column may be deleted.' is very vague.What do you mean by 'edit a table'? The course of action is to 'rebuild the primary index.' Does this mean the clustered index?Chris
    • Anonymous
      March 22, 2016
      The comment has been removed
      • Anonymous
        March 22, 2016
        The comment has been removed
  • Anonymous
    March 22, 2016
    I think of edit a table as right click on a table and select Edit Top 200 rows. Using ALTER TABLE would be different. So if you drop a variable length column and it deletes the data from another column how can ALTER INDEX REBUILD bring back the missing value?Chris
    • Anonymous
      March 22, 2016
      The comment has been removed
  • Anonymous
    March 22, 2016
    The comment has been removed
    • Anonymous
      March 24, 2016
      We've discussed this offline, and we will be updating the KB article to be more clear on the scenario and when to use the workaround, if the fix is not installed.Thanks again!
  • Anonymous
    March 23, 2016
    Would it be possible to get clarification whether or not Microsoft now recommends applying the latest CU to SQL Server in general now versus specific scenarios like in the past?https://www.pythian.com/blog/sql-server-cumulative-update-changes/It seems this verbiage changed in SQL Server 2012 SP3 CU1, but the SQL Server servicing model, SQL Server update center, MSDN/TN blogs nor previous service pack articles seem to make mention or clarify this.The only clarification seems to come from whoever runs the excellent Blogger site for SQL build versions.sqlserverbuilds.blogspot.com"Cumulative Update; Cumulative updates contain the bug fixes and enhancements–up to that point in time–that have been added since the previous Service Pack release and will be contained in the next service pack release. Installation of the Cumulative Update is similar to the installation of a Service Pack. Cumulative Updates are not fully regression tested.* Since January 27, 2016: Microsoft recommends ongoing, proactive installation of SQL Server CUs as they become available. SQL Server CUs are certified to the same levels as Service Packs, and should be installed with the same level of confidence."
    • Anonymous
      March 24, 2016
      A post just now posted should address this, thank you! Additionally, various MSDN and Knowledge Base articles are being updated to reflect these changes.
      • Anonymous
        March 24, 2016
        Perfect. Thank you!