SQL Server 2014 Service Pack 3 release information

Applies to: SQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 Enterprise Core More

This article contains important information to read before you install Microsoft SQL Server 2014 Service Pack 3 (SP3). It describes how to get the service pack, the list of fixes that are included in the service pack, known issues, and a list of copyright attributions for the product.

Note This article serves as a single source of information to locate all documentation that's related to this service pack. It includes all the information that you previously found in the release notes and Readme.txt files.

More Information


How to get SQL Server 2014 SP3

SQL Server 2014 SP3 and Microsoft SQL Server 2014 SP3 Express are available for manual download and installation at the following Microsoft Download Center websites.

SQL Server 2014 SP3 Download Download the package now.
SQL Server 2014 SP3 Express Download Download the package now.


Note After you install the service pack, the SQL Server service version should be 12.0.6024.0 Microsoft SQL Server 2014 service packs are cumulative updates. SQL Server 2014 SP3 upgrades all editions and service levels of SQL Server 2014 to SQL Server 2014 SP3.

For more information about the cumulative updates that are available in SQL Server 2014, see SQL Server 2014 build versions.

List of improvements and fixes included in SQL Server 2014 SP3

Microsoft SQL Server 2014 service packs are cumulative updates. SQL Server 2014 SP3 upgrades all editions and service levels of SQL Server 2014 to SQL Server 2014 SP3. In addition to the fixes that are listed in this article, SQL Server 2014 SP3 includes hotfixes that were included in SQL Server 2014 Cumulative Update 1 (CU1) to SQL Server 2014 SP2 CU13.

Notes

  • Additional fixes that aren't documented here may also be included in the service pack.
  • This list will be updated when more articles are released.

For more information about the bugs that are fixed and enhancements that are included in SQL Server 2014 SP3, go to the following Microsoft Knowledge Base articles.

VSTS bug number KB article number Description
11275485 3136242 FIX: New TCP connection is established and remains open until the process is terminated in SSIS 2014
10645271 4046870 Improvement: Replace HTTP URLs with HTTPS URLs in SQL Server 2014 Installation Wizard to improve security
12144118 4338890 FIX: "Non-yielding Scheduler" error and SQL Server appears unresponsive in SQL Server 2014, 2016 and 2017
6589008 3107173 Improved memory grant diagnostics using Extended Events in SQL Server 2012 and 2014
10065120 3136496 FIX: Access violation occurs when a query references an SQLCLR function through a synonym in SQL Server 2014 and 2016
10766202 3170019 Update to add info about SQL Server startup account to security policy in SQL Server 2012 and 2014 error log
10766201 3170020 Informational messages added for tempdb configuration in the SQL Server error log in SQL Server 2012 and 2014
10766203 3170115 Information about enabled trace flags is added to the showplan XML in SQL Server
10766207 3170116 FIX: Memory grant that's required to run optimized nested loop join isn't reflected in Showplan XML in SQL Server
11441121 3173157 Adds a stored procedure for the manual cleanup of the change tracking side table in SQL Server
10766200 3191296 Update extends the Trace extended event with security protocol handshake information in SQL Server
10766205 3201552 Update adds overall query execution statistics information to the STATISTICS XML output in SQL Server 2012, 2014 and 2016
10766190 4013128 FIX: Decreased performance and long waits for CLR_AUTO_EVENT and CMEMTHREAD when SQLCLR UDT is used as a stored procedure parameter for a SQL RPC call
10766206 4016867 FIX: Data types of Query_hash and Query_hash_plan columns in xEvents do not match the data types in DMVs sys.dm_exec_requests and sys.dm_exec_query_stats
10766208 4016949 Unified Showplan Schema for different versions of SQL Server
9956168 4018930 Update adds the "CLR strict security" feature to SQL Server
11504303 4038113 FIX: EXCEPTION_ACCESS_VIOLATION for query using sys.dm_os_memory_objects statement in SQL Server
10766227 4038210 FIX: Change Data Capture stops working after a recent cumulative update for SQL Server is installed
8862297 4038418 Update adds a new column to DMV sys.dm_sql_referenced_entities in SQL Server 2014 and 2016
11061754 4038419 Update adds CPU timeout setting to Resource Governor workgroup REQUEST_MAX_CPU_TIME_SEC in SQL Server 2014, 2016 and 2017
11061701 4041809 Update adds support for MAXDOP option for CREATE STATISTICS and UPDATE STATISTICS statements in SQL Server 2014, 2016 and 2017
11061712 4041811 FIX: Automatic update of incremental statistics is delayed in SQL Server 2014, 2016 and 2017
11990860 4042415 FIX: Deadlock occurs on single-user mode database when many connections access it simultaneously in SQL Server 2014 and 2016
11542219 4042788 FIX: The tempdb system database is still encrypted after you turn off encryption on an instance of SQL Server
11715407 4051360 FIX: Execution stats of scalar user-defined function is added to Showplan XML file in SQL Server 2016 SP2
11715377 4051361 Optimizer row goal information in query execution plan added in SQL Server 2014, 2016 and 2017
11441136 4052129 Optimizer row goal information in query execution plan added in SQL Server 2014, 2016 and 2017
10766239 4056008 FIX: "sp_special_columns" returns incorrect result in SQL Server 2014 and 2016
11821775 4088193 FIX: Slow restore performance when restoring a compressed backup on a disk with 4K sector size in SQL Server
11814300 4099472 PFS page round robin algorithm improvement in SQL Server 2014, 2016 and 2017
11971859 4316858 FIX: "Corrupted index" message and server disconnection when an update statistics query uses hash aggregate on SQL Server
10895916 4092075 Improvement: Adds Service Broker support for DBCC CLONEDATABASE in SQL Server

Notes for this update


Additional resolutions

Resolutions to the following issues are also included in SQL Server 2014 SP3.
 
VSTS bug number Description

10766220

Fixes an issue in which distribution agent failed with 20598 (row not found) error when applying the replicated command
10656209 Fixes an issue in which Access violation occurred when reading from audit trace
10762682

Fixes an issue in which SQL Server crushed with assertion message when using the top script with negative number

5646575 Fixes an issue in which SQL Server returns records multiple times when the query used the date types which decimal or numeric together with int.
7800206 Fixes an issue in which ShortestLineTo() method returns incorrect result for the shortest distance.
10288772 Fixes 1828 error when Adding more than one database file with the same logical name.
10355597 Fixes an issue in which memory leaks when an exception has been thrown.
10472856 Fixes an issue in which access violation occurs when using the script that have filter expression for filtered index and stats
11990862 Fixes an issue in which you cannot get the database name in extended event xml_deadlock_report, it always display master database.
11970514 You can create target table in filegroup by SELECT INTO script.
11542215 Add more underlying processor information (such as number of sockets, number of physical cores on a socket, number of NUMA nodes) in the sys.dm_os_sys_info dynamic management view.
11565697 Expose last successful execution of the DBCC CHECKDB command in the sys.databases system catalog view.
11007718 Raise an error message when execute an UPDATE statement that references a non-existing partition function using the $PARTITION keyword.
11269484 Adds the filegroup support to the SELECT INTO statement. This allows you to specify the name of the filegroup in which a new table will be created. The filegroup specified should exist on the database else the SQL Server engine throws an error.
11542000 Adds a new DMV sys.dm_db_log_stats that returns summary level attributes and information about transaction log files of databases.
11542049 Adds a new DMV sys.dm_db_log_info that returns the Virtual Log File (VLF) information about the transaction log files.
11542050 Exposes the percentage of differential changes in the databases to help determine whether full database backup or differential backup is useful.
11542051 sys.dm_tran_version_store_space_usage
11542121 Improves the backup performance on computers that have large memory.
11542133 Ensure database name information always included in the deadlock graph.

 

Select the correct file to download and install

The SQL Server 2014 SP3 download page contains the system requirements for installing SQL Server 2014 SP3 and basic installation instructions. For additional documentation about how to upgrade installed 2014 SP3 components with a SQL Server 2014 servicing update, see Install SQL Server 2014 Servicing Updates.

Use the following table to identify the location and name of the file to download based on your currently installed version. The download pages provide system requirements and basic installation instructions. 
 

Version you currently have installed Action you want to take File to download and install
A 32-bit version of any edition of SQL Server 2014 Upgrade to the 32-bit version of SQL Server 2014 SP3 SQLServer2014SP3-KB3587061-x86-ENU.exe from here
A 32-bit version of SQL Server 2014 RTM or SP1 Express or SP2 Express Upgrade to the 32-bit version of SQL Server 2014 Express SP3 SQLServer2014SP3-KB3587061-x86-ENU.exe from here
A 32-bit version of only the client and manageability tools for SQL Server 2014 (including SQL Server 2014 Management Studio) Upgrade the client and manageability tools to the 32-bit version of SQL Server 2014 SP3 SQLManagementStudio_x86_ENU.exe from here
A 32-bit version of SQL Server 2014 Management Studio Express Upgrade to the 32-bit version of SQL Server 2014 SP3 Management Studio Express SQLManagementStudio_x86_ENU.exe from here
A 32-bit version of any edition of SQL Server 2014 and a 32-bit version of the client and manageability tools (including SQL Server 2014 RTM Management Studio) Upgrade all products to the 32-bit version of SQL Server 2014 SP3 SQLServer2014SP3-KB3587061-x86-ENU.exe from here
No 32-bit installation of SQL Server 2014 Management Studio Install 32-bit SQL Server 2014 Management Studio including SP3 SQLManagementStudio_x86_ENU.exe from here
No 32-bit version of SQL Server 2014 Express Install 32-bit SQL Server 2014 Express including SP3 SQLEXPR32_x86_ENU.exe from here
A 64-bit version of any edition of SQL Server 2014 Upgrade to the 64-bit version of SQL Server 2014 SP3 SQLServer2014SP2-KB3587061-x64-ENU.exe from here
A 64-bit version of SQL Server 2014 RTM or SP1 Express or SP2 Express Upgrade to the 64-bit version of SQL Server 2014 SP3 SQLServer2014SP2-KB3587061-x64-ENU.exe from here
A 64-bit version of only the client and manageability tools for SQL Server 2014 (including SQL Server 2014 Management Studio) Upgrade the client and manageability tools to the 64-bit version of SQL Server 2014 SP3 SQLManagementStudio_x64_ENU.exe from here
A 64-bit version of SQL Server 2014 Management Studio Express Upgrade to the 64-bit version of SQL Server 2014 SP3 Management Studio Express SQLManagementStudio_x64_ENU.exe from here
A 64-bit version of any edition of SQL Server 2014 and a 64-bit version of the client and manageability tools (including SQL Server 2014 RTM Management Studio) Upgrade all products to the 64-bit version of SQL Server 2014 SP3 SQLServer2014SP2-KB3587061-x64-ENU.exe from here
No 64-bit installation of SQL Server 2014 Management Studio Install 64-bit SQL Server 2014 Management Studio including SP3 SQLManagementStudio_x64_ENU.exe from here
No 64-bit version of SQL Server 2014 Express Install 64-bit SQL Server 2014 Express including SP3 SQLEXPR_x64_ENU.exe from here

 

For more information about how to upgrade your SQL Server installation to SQL Server 2014 SP3, see Supported Version and Edition Upgrades.

Uninstalling SQL Server 2014 SP3 (not recommended)

If, for any reason, you choose to uninstall SQL Server 2014 SP3, the uninstallation of SQL Server 2014 SP3 will not be blocked, and you will be able to uninstall SQL Server 2014 SP3 in the same manner as any other service packs. However, if you are running the Standard, Web, or Express edition of SQL Server, and you are using some new features that are unlocked only when you start SQL Server 2014 SP3, you might experience errors or see databases left in a suspect state after the uninstallation of SQL Server 2014 SP3. Even worse, if the system databases are using new features (for example, partitioned tables in master databases), this could prevent SQL Server instances from starting after you uninstall SQL Server 2014 SP3.

We recommend that you verify that all the new features are disabled or dropped before you choose to uninstall SQL Server 2014 SP3 on editions other than the Enterprise edition. You cannot drop the memory_optimized_data filegroup. Therefore, if you have set up the memory_optimized_data filegroup on your database with SP2, you should not uninstall SQL Server 2014 SP3. Otherwise, the database will get into a suspect state, and the following entry will be logged in the error log:

DateTime spid15s Error: 41381, Severity: 21, State: 1.
DateTime spid15s The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions.
 

References


For more information about how to determine the current SQL Server version and edition, select the following article number to go to the article in the Microsoft Knowledge Base:

321185 How to identify your SQL Server version and edition