List of Bugs Fixed in SQL Server 2014 SP1 – Part 4
With every release of SQL Server product or subsequent service packs or Cumulative updates, new bugs are encountered or discovered. Below are some of the bugs which were fixed with the release of Service Pack 1 (SP 1) for Microsoft SQL Server 2014.
VSTS BUG Number 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.
VSTS BUG Number 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.
VSTS BUG Number 2535853
/qs option requires user input when you install Express packages of SQL Server 2014 RTM.
VSTS BUG Number 2580641
Invalid query syntax in stored procedure when you drop an article that is published in
more than one publication.
VSTS BUG Number 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.
VSTS BUG Number 2580686
Update-Update conflicts in P2P replication when updates are made to text column by using UPDATE or WRITE.
VSTS BUG Number 2580693
Incorrect results when you work with block mode unary operators.
VSTS BUG Number 2580746
DPM’s full backup on the server with AlwaysOn secondary will be converted to copy_only backup
VSTS BUG Number 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.
Hope this was helpful.
This is applicable for below versions of SQL Server
SQL Server 2014
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings