November 2014 Cumulative Updates for SQL Server 2012

Microsoft has released Cumulative Updates for SQL Server 2012 Service Pack 1 and Service Pack 2. Note that RTM is no longer supported and you should be moving to the SP2 branch soon.

SQL Server 2012 Service Pack 1 Cumulative Update #13

  • KB #3002044
  • Build #11.0.3482
  • 13 fixes (10 public)
  • Relevant for Service Pack 1 only (11.0.3000 -> 11.0.3481)

SQL Server 2012 Service Pack 2 Cumulative Update #3

  • KB #3002049
  • Build #11.0.5556
  • 40 fixes (33 public)
  • Relevant for Service Pack 2 only (11.0.5058 -> 11.0.5555)

For more information about SQL Server 2012 builds, see this blog post on blogs.sentryone.com.

Aaron Bertrand

I am a passionate technologist with industry experience dating back to Classic ASP and SQL Server 6.5. I am a long-time Microsoft MVP, speak frequently at conferences, and write at SQLPerformance and MSSQLTips. In real life I am an architect at Wayfair.

3 Responses

  1. Sankar Reddy says:

    Hi Aaron,
    FYI. Sharing info here so that others can be prepared just in case if this happens to them.
    I had one of the dev servers died on me when applying the CU3. Had to rebuild the system databases. Prior to this, I have successfully applied this CU to many dev, production servers.
    2014-11-20 08:06:03.83 spid4s      Database 'master' is upgrading script 'upgrade_ucp_cmdw_discovery.sql' from level 184554434 to level 184554932.
    2014-11-20 08:06:04.47 spid4s      Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184554434 to level 184554932.
    2014-11-20 08:06:04.47 spid4s      ———————————-
    2014-11-20 08:06:04.47 spid4s      Starting execution of PRE_MSDB.SQL
    2014-11-20 08:06:04.47 spid4s      ———————————-
    2014-11-20 08:06:04.75 spid4s      Error: 15002, Severity: 16, State: 1.
    2014-11-20 08:06:04.75 spid4s      The procedure 'sys.sp_dbcmptlevel' cannot be executed within a transaction.
    2014-11-20 08:06:04.75 spid4s      —————————————–
    2014-11-20 08:06:04.75 spid4s      Starting execution of PRE_SQLAGENT100.SQL
    2014-11-20 08:06:04.75 spid4s      —————————————–
    2014-11-20 08:06:04.75 spid4s      Error: 226, Severity: 16, State: 6.
    2014-11-20 08:06:04.75 spid4s      ALTER DATABASE statement not allowed within multi-statement transaction.
    2014-11-20 08:06:04.75 spid4s      The failed batch of t-sql statements :
    –set compatibily level to 110
    ALTER DATABASE msdb
     SET COMPATIBILITY_LEVEL = 110
    2014-11-20 08:06:04.75 spid4s      Error: 912, Severity: 21, State: 2.
    2014-11-20 08:06:04.75 spid4s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 226, state 6, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
    2014-11-20 08:06:04.76 spid4s      Error: 3417, Severity: 21, State: 3.
    2014-11-20 08:06:04.76 spid4s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

  2. Chris Wood says:

    Wonder if this issue is related to this fix in SP1 CU13 http://support.microsoft.com/kb/3013551
    Chris

  3. Alex Averin says:

    I have 11.0.2218.0 of MS SQL Server Standard Edition (64-bit). Which update do I need to install? Thank you in advance.