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.
SQL Server Connect BUG Number 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.
SQL Server Connect BUG Number 735543
Database goes into a restore mode when its backup is restored as a different database on the same instance.
SQL Server Connect BUG Number 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.
SQL Server Connect BUG Number 740181
SSMS does not fully manage Full-Text in SQL Server Express.
SQL Server Connect BUG Number 745566
SQL Server SMO ignores default constraint in SQL Server 2012 and SQL Server 2014.
SQL Server Connect BUG Number 764197
SSMS handles Numbered Stored procedures inconsistently.
SQL Server Connect BUG Number 769121
SQL Server Connect BUG Number 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.
SQL Server Connect BUG Number 774317
SSMS occasionally crashes on close, which then causes it to automatically restart
SQL Server Connect BUG Number 785064
“Value of ‘null’ is not valid for ‘stream’ ” error message when you work with customer pipeline components in Business Intelligence Development Studio (BIDS).
SQL Server Connect BUG Number 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.
SQL Server Connect BUG Number 791929
“A system assertion check has failed” error message when you insert data into a partitioned view that has triggers.
SQL Server Connect BUG Number 797967
Create script duplicates the statements when scripting column level permissions in SSMS.
SQL Server Connect BUG Number 799430
SSMS may crash when you try to refresh the SSMS window icon on the task bar.
SQL Server Connect BUG Number 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.
SQL Server Connect BUG Number 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.
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