Related topics
×
Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

This article contains important information to read before you install Microsoft SQL Server 2014 Service Pack 1 (SP1). It describes how to obtain the service pack, the list of fixes that are included in the service pack, how to select the correct download based on your currently installed version, and a list of copyright attributions for the product.

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

Note If you are trying to update your instance from Cumulative Update 11 for SQL Server 2014 (build number 12.0.2560.0) to SQL Server Service Pack 1, the service pack setup fails because of binary mismatch between SQLServr.exe and qds.dll files and SQL Server cannot be started after that.

To work around the issue, use one of the following methods:

  • To continue staying on Cumulative Update 11 for SQL Server 2014, you can uninstall the incomplete Service Pack installation. To do this, use Add or Remove Programs in Control Panel and then restart SQL Server.

  • To upgrade to Service Pack 1 from CU11 and still retain the fixes through CU11, follow these steps:

    1. Uninstall CU11 by using Add or Remove Programs in Control Panel.

    2. Download and install SP1 from the download center at Microsoft SQL Server 2014 Service Pack 1 (SP1).

    3. Download and install CU4 for SP1 from Cumulative Update 4 for SQL Server 2014 SP1.


More Information

How to obtain SQL Server 2014 SP1

SQL Server 2014 SP1 is available for download at the SQL Server 2014 SP1 download page. You can download SQL Server 2014 SP1 Feature Pack here.



Note After you install the service pack, the SQL Server service version should be reflected as 12.0.4100.1.

List of fixes included in SQL Server 2014 SP1

Microsoft SQL Server 2014 service packs are cumulative updates. SQL Server 2014 SP1 upgrades all editions and service levels of SQL Server 2014 to SQL Server 2014 SP1.

In addition to the fixes that are listed in this article, SQL Server 2014 SP1 includes hotfixes that were included in SQL Server 2014 CU1 to SQL Server 2014 CU 5.

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

Notes

  • Additional fixes that are not 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 in SQL Server 2014 SP1, click the following links to view the articles in the Microsoft Knowledge Base.

VSTS bug number

KB article number

Description

2275929

3044954

FIX: Access violation occurs on the I/O Completion routine when you enable AutoClose in SQL Server 2014

2364636

2969781

FIX: Error when you add a custom connection manager in SSIS 2014 Designer

2580631

2963404

FIX: Rollback causes database to go to suspect mode in SQL Server 2012 or SQL Server 2014

2580750

2806979

FIX: Poor performance when you run a query against a table in an RCSI-enabled database in SQL Server 2012 or 2014

2580628

2965035

SSAS 2012 logging feature improvement in SQL Server 2012 Service Pack 2

2581015

2963412

New DMF sys.dm_fts_index_keywords_position_by_document in SQL Server 2012 SP2 and SQL Server 2014 SP1

2581019

2966520

FIX: New log files are not created when you restart the Reporting Services Windows Service in SSRS on January 1

2581025

3051521

FIX: "Database 'model' cannot be opened" error when you restart SQL Server after tail-log backup for model database

2581225

2964762

FIX: Event ID 22 or error 0xC1000016 will be logged when you use the Discover command in SSAS 2012

2581168

2966522

FIX: File Share subscription doesn't populate the description column in SSRS 2012 or SSRS 2014

2581259

2966523

FIX: The "Name" drop-down list is empty when a report is specified in SSRS 2012 or SSRS 2014

2581317

2963382

FIX: Can't connect to the server when you run a cube creation MDX query in SSAS 2012 or SSAS 2014

2581323

2963384

FIX: SQL Server crashes when the log file of tempdb database is full in SQL Server 2012 or SQL Server 2014

2581360

2927741

FIX: Image is not displayed correctly in the webpage when you use DrillThrough action on an SSRS 2012 or 2014 report

2581371

2963383

FIX: Text truncated when you use HPB renderer to view a report in SSRS 2012 or in SSRS 2014

2700155

3044958

FIX: Rollback recovery on a snapshot fails when you run DBCC CHECKDB and then SQL Server shuts down unexpectedly

3860819

3030619

FIX: Incorrect data returned when you use DATE data type as a qualifier in a query in SQL Server 2014

3879685

3020112

FIX: Non-yielding error occurs when you execute DML statements in SQL Server 2014

3919713

3027860

Error 17066 or 17310 during SQL Server startup

3933346

3044953

FIX: Non-yielding scheduler issue when you write pages to buffer pool extension file in SQL Server 2014

4011750

3029977

FIX: OS error 665 when you execute DBCC CHECKDB command for database that contains columnstore index in SQL Server 2014

4033440

3021757

FIX: Duplicate sequence value is generated when you run sp_sequence_get_range in parallel with NEXT VALUE FOR function

4034813

3029825

FIX: DBCC CHECKDB and DBCC CHECKTABLE take longer to run when SQL CLR UDTs are involved in SQL Server 2012 or SQL Server 2014

4050109

3026082

FIX: SOS_CACHESTORE spinlock contention on system table rowset cache causes high CPU usage in SQL Server 2012 or 2014

4075490

3034679

FIX: AlwaysOn availability groups are reported as NOT SYNCHRONIZING

4093558

3035165

FIX: Error 8646 when you run DML statements on a table with clustered columnstore index in SQL Server 2014

3534419, 3534439, 2512250, 1456033, 2274636

3044952

FIX: Issues when you enable the buffer pool extension feature in SQL Server 2014

3731772, 3731776

3044519

FIX: Query performance issues when new cardinality estimator is enabled in SQL Server 2014

2581312

2904152

FIX: Consuming reports on a remote farm does not work in SharePoint Integrated for a published SSRS 2014 Service application

Additional resolutions

Resolutions to the following issues are also included in SQL Server 2014 SP1.

VSTS bug number

Description

1957464

RESTORE HEADERONLY for an Encrypted Backup file of the Database does not show whether the backup is encrypted or not.
After you apply SP1, the output of RESTORE HEADONLY will include three additional columns: KeyAlgorithm, EncryptorThumbprint and EncryptorType that can give additional details about the encrypted backup. For more information, see RESTORE HEADERONLY topic in SQL Server Books Online.

2366022

SQL Server setup required the .NET Framework 3.5 when you install SQL Server 2014 Express Edition (with Database Engine only) on Windows 8. It is now skipped when you install this kind of media.

2535853

/qs option requires user input when you install Express packages of SQL Server 2014 RTM.

2580641

Invalid query syntax in stored procedure when you drop an article that is published in
more than one publication.

2580651

Peer-to-peer (P2P) conflict messages require additional details.

Note After you apply SP2 for 2012 or SP1 for 2014, the error message 22815 will have the information on Table Name, Primary Key (s), Current Version, Pre Version and Post Version. Apart from Table Name and Primary Key(s), Post Version exists for all three types of conflict (delete, update and insert). Current Version is not applicable for delete conflict type and PreVersion is not applicable for exist for insert conflict type.

2580686

Update-Update conflicts in P2P replication when updates are made to text column by using UPDATE or WRITE.

2580693

Incorrect results when you work with block mode unary operators.

2580746

DPM’s full backup on the server with AlwaysOn secondary will be converted to copy_only backup

2581191

Merge Replication logging improvement:
To help troubleshoot merge replication performance issues, add the output of TraceFlag 101 when the output verbose level for the merge agent is set to 4.

2581192

Transaction Replication logging improvement:
To help troubleshoot transaction replication performance issues, add verbose message to the stats in history tables and more detailed messages in the agent logs.

2581222

SSMS Crashes during Movement of Maintenance Plan tasks if the Maintenance Plan name the first SUB_PLAN name are the same.

2581197

The end SCOPE statement does not match the opening SCOPE statement.

2581377

"ACTIONABLE_HEAP_CORRUPTION" when SSRS configuration file is parsed by using an invalid InstanceId.

2581382

Provides platform information in the log of SSRS 2014

2733205

"Action <name> was not found" message when selecting Facets option from the context menu of a Report Server instance in object explorer

2841734

Exception occurs when you execute the SQL Server 2014 cumulative update package (for example SQLServer2014-KB2967546-x64.exe) with the command-line switch /?

3143194

LOB reads are shown as zero when "SET STATISTICS IO" is on during executing a query with clustered columnstore index.

3506361

Some shared components could not be patched for later servicing when SSDT BI version 12.0.2299.1 and SQL Server 2014 are installed side by side.

3731350

When you use features that rely on log pool cache (for example, Always On) on systems with multiple sockets, you may notice high values for "log write waits" counter. Before SP1, you have to enable trace flag T9024 to activate the fix for this issue in SQL Server 2014. Starting SP1, you do not have to manually add the trace flag, as the fix is already included. For more information, see FIX: High "log write waits" counter value on an instance of SQL Server 2012.

3732057

When your instance of SQL Server is handling thousands of connection resets because of connection pooling, performance problems occur when database lock activity increases in SQL Server. The issue is fixed in CU1 for SQL Server 2014, and you have to add a trace flag T1236 to start parameters to activate the fix. Service Pack 1 for SQL Server 2014 includes this fix by default and you do not have to add any trace flags to activate the fix. For more information, see FIX: Performance problems occur when database lock activity increases in SQL Server.

3909490

Error 4819 occurs for some combination of database schema and data when the fast load context (TF610) for bulk load and TF4199 are enabled.

3938420

Cannot upgrade a SQL Server instance to SQL Server 2014 because SQL Server Agent JOBS directory is missing, and the system is in an incomplete state.

Fixes for Connect Items

The following fixes for Connect Items were submitted by the community and are also included in SQL Server 2014 SP1.

Connect Bug ID

Description

714689

Evaluation results are written to output xml file multiple times when you implement Enterprise Management Framework against multiple servers and an error occurs against one of the servers in the list.

735543

Database goes into a restore mode when its backup is restored as a different database on the same instance.

736509

You cannot debug a stored procedure that calls sp_executesql in SQL Server Management Studio (SSMS). When F11 is pressed, you receive an 'Object reference not set to an instance of object' error message.

740181

SSMS does not fully manage Full-Text in SQL Server Express.

745566

SQL Server SMO ignores default constraint in SQL Server 2012 and SQL Server 2014.

764197

SSMS handles Numbered Stored procedures inconsistently.

769121

"Column '<column name>' does not belong to table summary. (System.Data)" error message when replicating tables have the same names but are located in different schemas.

773710

After reverting to a database snapshot that contains full-text indexes, you cannot create any ft_catalogs until you either restart SQL Server, detach and then attach the database, or take the database offline and then set the database online.

774317

SSMS occasionally crashes on close, which then causes it to automatically restart

785064

"Value of 'null' is not valid for 'stream' " error message when you work with customer pipeline components in Business Intelligence Development Studio (BIDS).

785151

When you execute queries with Show Actual Query Plan turned on, the result of Null is returned, and you receive the following error message:
Error: Msg 50000, Level 16, State 10, Procedure test, Line 34 String or binary data would be truncated.

791929

"A system assertion check has failed" error message when you insert data into a partitioned view that has triggers.

797967

Create script duplicates the statements when scripting column level permissions in SSMS.

799430

SSMS may crash when you try to refresh the SSMS window icon on the task bar.

804901

Deploying new versions of large projects encounters a time-out during deployment into SSIS Catalog database (SSISDB). Additionally, you receive the following error messages:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier ’219′. (Microsoft SQL Server, Error: 27203) Failed to deploy the project. Fix the problems and try again later.:Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

805659

"Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries" error message when you parse or execute stored procedure.

Select the correct file to download and install

The SQL Server 2014 SP1 download page contains the system requirements for installing SQL Server 2014 SP1 and basic installation instructions. For additional documentation about how to upgrade installed 2014 SP1 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 SP1

SQLServer2014SP1-KB3018269-x86-ENU.exe from here

A 32-bit version of SQL Server 2014 RTM Express

Upgrade to the 32-bit version of SQL Server 2014 Express SP1

SQLServer2014SP1-KB3018269-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 SP1

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 SP1 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 SP1

SQLServer2014SP1-KB3018269-x86-ENU.exe from here

A 32-bit version of one or more tools from the Microsoft SQL Server 2014 RTM Feature Pack

Upgrade the tools to the 32-bit version of Microsoft SQL Server 2014 SP1 Feature Pack

One or more files from Microsoft SQL Server 2014 SP1 Feature Pack

No 32-bit installation of SQL Server 2014 Management Studio

Install 32-bit SQL Server 2014 Management Studio including SP1

SQLManagementStudio_x86_ENU.exe from here

No 32-bit version of SQL Server 2014 RTM Express

Install 32-bit SQL Server 2014 Express including SP1

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 SP1

SQLServer2014SP1-KB3018269-x64-ENU.exe from here

A 64-bit version of SQL Server 2014 RTM Express

Upgrade to the 64-bit version of SQL Server 2014 SP1

SQLServer2014SP1-KB3018269-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 SP1

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 SP1 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 SP1

SQLServer2014SP1-KB3018269-x64-ENU.exe from here

A 64-bit version of one or more tools from the Microsoft SQL Server 2014 RTM Feature Pack

Upgrade the tools to the 64-bit version of Microsoft SQL Server 2014 SP1 Feature Pack

One or more files from Microsoft SQL Server 2014 SP1 Feature Pack

No 64-bit installation of SQL Server 2014 Management Studio

Install 64-bit SQL Server 2014 Management Studio including SP1

SQLManagementStudio_x64_ENU.exe from here

No 64-bit version of SQL Server 2014 RTM Express

Install 64-bit SQL Server 2014 Express including SP1

SQLEXPR_x64_ENU.exe from here

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

Note If you have version 12.0.4050.0 of SQL Server 2014 Service SP1 (KB3018269) installed, you must uninstall that update from all installation instances before you install this update. To do this, use Add or Remove Programs in Control Panel. For more information, see KB 3018269. Notice that you may have KB3018269 installed for any of the following reasons:

  • You applied the update to an existing instance of SQL Server 2014

  • You installed a new instance of SQL Server 2014 SP1 by using the KB3018269 “Slipstream Package” (for example, SQLServer2014SP1-FullSlipstream-x64-ENU)

  • You installed any of the SQL Server 2014 SP1 Express Edition packages

  • This product contains software derived from the Xerox Secure Hash Function.

  • This product includes software from the zlib general purpose compression library.

  • Parts of this software are based in part on the work of RSA Data Security, Inc. Because Microsoft has included the RSA Data Security, Inc., software in this product, Microsoft is required to include the text below that accompanied such software:

    • Copyright 1990, RSA Data Security, Inc. All rights reserved.

    • License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc., MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc., MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work.

    • RSA Data Security, Inc., makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind.

    These notices must be retained in any copies of any part of this documentation or software.

  • The Reporting Services mapping feature uses data from TIGER/Line Shapefiles that are provided courtesy of the U.S. Census Bureau (http://www.census.gov/). TIGER/Line Shapefiles are an extract of selected geographic and cartographic information from the Census MAF/TIGER database. TIGER/Line Shapefiles are available without charge from the U.S. Census Bureau. To obtain more information about the TIGER/Line shapefiles, go to http://www.census.gov/geo/www/tiger. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only; its depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority, rights of ownership, or entitlement, and does not reflect legal land descriptions. Census TIGER and TIGER/Line are registered trademarks of the U.S. Bureau of the Census.

Copyright 2012 Microsoft. All rights reserved.

References

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

321185
How to identify your SQL Server version and edition
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×