次の方法で共有

SQL Server 2012 Service Pack 3 is now Available!

  • [アーティクル]

Microsoft is pleased to announce the release of SQL Server 2012 Service Pack 3. This service pack provides updates to help workloads from a performance, scalability and diagnostics perspective. The key updates are listed below.

Improvements for performance and scalability

  • Trace flags 1236 and 9024 were introduced in SQL Server 2012 to address lock contention and log write waits for systems with high number of transactions. SQL Server 2012 SP3 makes this behavior default without having to use the trace flags. This ensures that your system is able to scale up when required without any user action required. The default behavior was already introduced in SQL Server 2014 Service Pack 1.
  • Improvements to consistency check performance by estimating memory grants correctly and making optimum use of CPU and Memory (KB3029825).
  • Improvements while performing a SELECT INTO operation involving a temporary table. This is a common scenario when database operations involve temporary or staging tables.
  • Added new query hints for Resource Governor through MIN_GRANT_PERCENT and MAX_GRANT_PERCENT (KB3107401). This allows you to leverage these hints while running queries by capping their memory grants to prevent memory contention.
  • Improvements to enhance the performance of opening and reading the (.xel) Extended Event files (KB3112710). This allows you to analyze data faster while troubleshooting SQL Server related issues.
  • If you use spatial data in your application, then SP3 has improvements for spatial query performance (KB3107399).

Improved diagnostic and troubleshooting capabilities

  • Added new logging capability for Lease Timeout messages so that the current time and the expected renewal times are logged.
  • There is a new error message for lease workers that clearly indicates the reason for the Lease Timeout. This would allow you to troubleshoot failover issues more effectively.
  • Lease stages for Availability Groups are now indicated through new extended events for lease workers.
  • Improvements in non-yield detection logic to prevent false positives for scheduler non-yield messages.
  • Improved diagnostic messages while performing backups using third-party applications that make use of SQLVDI.DLL.

Improvements for query performance troubleshooting

  • Sys.dm_exec_query_stats DMV will now report (KB3107398) information on memory grants, degree of parallelism and the threads used for executing the query. This information is normally available in the XML plan which can be now retrieved using the DMV as well.
  • Spills originating from SORT operations are reported correctly while tracking execution statistics. Now, SET STATISTICS IO option now exposes information about SORT operations.
  • The actual rows read will now be reported in the query execution plans (KB3107397) to help improve query performance troubleshooting. This should negate the need to capture SET STATISTICS IO separately. This now allows you to see information related to a residual predicate pushdown in a query plan.
  • Hash Warning and Sort Warnings now have additional columns to track physical I/O statistics, memory used and rows affected. We also introduced a new hash_spill_details extended event. Now you can track more granular information for your hash and sort warnings (KB3107172). This improvement is also now exposed through the XML Query Plans in the form of a new attribute to the SpillToTempDbType complex type (KB3107400).

We will be updating and adding follow-up posts on the Tiger blog in the coming weeks to describe some of the above improvements in detail.

As noted above, SP3 contains a roll-up of solutions provided in SQL Server 2012 cumulative updates up to and including the latest SP2 Cumulative Update - CU9 . Therefore, there is no requirement to wait for SP3 CU1 to ‘catch-up’
with 2012 SP2 CU content.

The Service Pack is available for download on the Microsoft Download Center, and will be made available via Microsoft Update on 8th December, 2015. It will also be available on MSDN, MAPS/MPN, MBS/Partner Source, and VLSC in the coming weeks. As part of our continued commitment to software excellence for our customers, this upgrade is available to all customers with existing SQL Server 2012 deployments.

To obtain SQL Server 2012 SP3, please visit the links below:

SQL Server 2012 SP3 SQL Server 2012 SP3 Express SQL Server 2012 SP3 Feature Packs SQL Server 2012 Service Pack 3 Release Information

Thank you,

Microsoft SQL Server Engineering Team

Comments

  • Anonymous
    November 25, 2015
    "this upgrade is available to all customers with existing SQL Server 2012 deployments." "Supported Operating System Windows 10 , Windows 8.1, Windows Server 2012 R2" So what happened to Windows Vista / 7 / 8 / 2008 / 2008 R2 / 2012 ?

  • Anonymous
    November 25, 2015
    Will there be a 2012 SP3 slipstreamed iso like there was for SP2?

  • Anonymous
    November 26, 2015
    Will the System Center Server 2012 R2 to support SQL Server 2012 SP3? technet.microsoft.com/.../dn281933.aspx

  • Anonymous
    November 26, 2015
    "So what happened to Windows Vista / 7 / 8 / 2008 / 2008 R2 / 2012 ?" I installed SP3 on my Server 2008 R2 yesterday -> works! :-)

  • Anonymous
    November 30, 2015
    @psc161: All operating systems listed in the following link are supported for SQL Server 2012 SP3: msdn.microsoft.com/.../ms143506(v=sql.110).aspx We will add the missing OS in the download page as well.

  • Anonymous
    December 02, 2015
    @psc161 OS Requirements have now been updated: Supported Operating System Windows 7, Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2 @asdf msdn.microsoft.com/.../downloads contains the slipstreamed ISOs @XYZ We are working with System Center on getting SP3 certified (and improving the process to include them in the internal partner RC testing)

  • Anonymous
    December 15, 2015
    I have a SQL 2012 server at level: 11.00.3349 (SP1 CU3) can i without problem upgrade this sever to SP3 ?

  • Anonymous
    December 17, 2015
    The comment has been removed

  • Anonymous
    December 27, 2015
    will the system center 2012 R2 support this SP3?

  • Anonymous
    January 11, 2016
    Tat SP3 introduced a bug :-( !!! When restoring to another database name and mdf/ldf names, that duplicated database runs fine but original database goes to no-ending restoration state and I fail to access it. Terrible! Original database should not be touched.

  • Anonymous
    January 15, 2016
    LaPeche35, can you share the steps that led to this state as this is unusual? Did you run the backup command with NORECOVERY option as this leaves the database in restoring state? To get the original database out of the recovering state, can you run the following command: RESTORE DATABASE youroriginaldbname WITH RECOVERY

  • Anonymous
    March 23, 2016
    Is SQL 2012 - SP3 support by SAP?

    • Anonymous
      March 24, 2016
      For SAP Netweaver, all SPs are always supported.

  • Anonymous
    March 29, 2016
    I receive the follow message when trying to download any SQL Server 2012 SP Gateway TimeoutThe proxy server did not receive a timely response from the upstream server.Reference #1.2583d717.1459265296.190a8dc5

  • Anonymous
    June 24, 2016
    We are currently running our Database Server on a RTM version:Microsoft SQL Server 2012 - 11.0.2100.60 (X64) Feb 10 2012 19:39:15 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.2 (Build 9200: ) (Hypervisor)We learnt that we need to install the latest Service Pack for SQL Server 2012, which is SP3I had the following doubts based on this subject:1. Will installation of SQL Server 2012 SP3 affect any of our production databases?2. Do we need to restore the databases, after installation of SP3?3. Are there any particular prerequisites we need to follow before the installation of SP3?4. Do we need to perform a database backup and backup of the data files before the installation of SP3?Please advise. Appreciate your help on this. Thanks.

    • Anonymous
      June 28, 2016
      Answers to your questions: 1. Will installation of SQL Server 2012 SP3 affect any of our production databases?A. I am not sure I completely understand this question. I will try to answer what I understood and if it's not sufficient, please reply back with additional questions in the comments section.. We do recommend that you perform application testing of all your application databases with Service Pack 3. Service Packs or any other updates for SQL Server do not make changes to the user data in the databases. 2. Do we need to restore the databases, after installation of SP3?A. No. Service Packs are in-place updates and do not require any database restores post the Service Pack installation. 3. Are there any particular prerequisites we need to follow before the installation of SP3?A. It is always recommended to have up-to-date backups of your databases (including system databases) before installing the update. You will require a downtime for installing the update as the installer stops and starts the SQL Server service. The databases will not be accessible to the application when the installation is running. 4. Do we need to perform a database backup and backup of the data files before the installation of SP3?A. Answered above.

  • Anonymous
    August 01, 2016
    Is there any risk of applying ServicePack 3 to SQL Server 2012 "Express" Edition?

    • Anonymous
      August 09, 2016
      No. There isn't.

  • Anonymous
    September 08, 2016
    The comment has been removed

    • Anonymous
      September 29, 2016
      Did you manage to resolve this issue? Or are you still unable to patch your servers with SP3. If yes, would it be possible to open a support incident so that our engineers can troubleshoot this further.
      • Anonymous
        December 04, 2016
        Hi Guys,I’m having an issues regarding the installation of 2012 SP3,last 6 hours still running. i have 4 instances still running (1 of 4) and installation very slow still running and show on production server msg -install_sql_rscpu64_action:installfiles.copyingnewfile. please provide me solution i am not understand when its completed,my downtime is 6 hours. so what can i do that situation please suggest
        • Anonymous
          December 28, 2016
          Typically for production issues, we recommend working with Microsoft Support for timely and SLA based response.

  • Anonymous
    May 11, 2017
    Hi Microsoft SQL Server support team,Yesterday evening our SQL environment went through upgrade SP2 to SP3. Current Version is ------------------------------------------------Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (X64) Oct 20 2015 15:36:27 Copyright (c) Microsoft CorporationEnterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 (Build 9200: ) (Hypervisor)------------------------------------------------We have observed some strange behaviour post update and below is the detailed description.We have Oracle DB and using the linked server we pull the data into Microsoft SQL server tables. We have created views on top of these Microsoft SQL server tables. These views are being used in Macros Query in EXCEL 2016 by end users, who refresh the excel every morning to see their data.Since this morning users starts reporting that data in excel was jumbled up (Example : 2.01802e+006) Correct Data value is 20180206We then started to look in to the data types in the Views, tables in Microsoft SQL server. We noticed that old data type of (nvarchar(384)), null) is now changed to (float, null). ( We created new table and data by droping the existing table, and recreating and repopulating using Query SELECT * INTO tablename FROM OPENQUERY(ABCDEF, 'select * from DATA'); (ABCDE is the linked server connection)We observed this same behavior of showing the data of type nvarchar(384) getting distorted on our other environment as well.Can you please look in to this and suggest workaround and long term solution. Apparently casting the column as float in table and view definition in SQL, is the quickest work around but we are talking about more than 300 columns and does not help. We have more than 700 users using this excel tool and this crooked data is causing real pain to their work.

    • Anonymous
      June 05, 2017
      Hello, We recommend opening a support case if these are production issues. In any case, it is not recommended to create a table between foreign RDBMS and SQL Server using SELECT...INTO, but rather manually to control data type mappings, or even using (SSMA 7.3.