KB3058865 - SQL Server 2014 Service Pack 1 release information

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.

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.