As of August 17, 2015, there have been two Cumulative Updates (CU) for the Service Pack 1 branch of SQL Server 2014. There were a large number of hotfixes in both cumulative updates. If you are running SQL Server 2014 SP1, I really think you should be running the latest SQL Server 2014 SP1 Cumulative Update. Right now, that means SP1, CU2 (Build 12.0.4422), which was released on August 17, 2015.
Note: SQL Server 2014 Service Pack 1 was re-released on May 4, 2015, and SQL Server 2014 SP1 CU2 was released on August 17, 2015. SQL Server 2014 SP1 CU2 is synchronized with SQL Server 2014 RTM CU9, so I think it is now ok to migrate to the SQL Server 2014 SP1 branch after you have done your own application testing and are ready to make that move.
Table 1 shows the SQL Server 2014 SP1 CU builds that have been released so far.
|12.0.4416||SP1 CU1||June 19, 2015|
|12.0.4422||SP1 CU2||August 17, 2015|
Table 1: SQL Server 2014 SP1 CU Builds
You can follow the KB article link below to see all of the CU builds for both the SQL Server 2014 RTM and the SQL Server 2014 SP1 branches.
Like I have done for other versions and branches of SQL Server, I decided to scan the hotfix list for all of the Cumulative Updates in the RTM branch, looking for performance and general reliability-related fixes for the SQL Server Database Engine. I came up with the list below, but this listing is completely arbitrary on my part. You may come up with a completely different list, based on what specific SQL Server 2014 features you are using.
Here are the fixes in the SP1 branch:
SQL Server 2014 SP1 Cumulative Update 1 (Build 12.0.4416), 112 total public hot fixes
SQL Server 2014 SP1 Cumulative Update 2 (Build 12.0.4422), 44 total public hot fixes
The reason that I put these lists together is that I want to convince more people to try to keep their SQL Server instances up to date with Cumulative Updates. If you do the proper testing, planning and preparation, I think the risks from installing a SQL Server Cumulative Update are quite low (despite the occasional issues that people run into).
If you install a Cumulative Update or Service Pack on a Production system the day it is released, after doing no testing whatsoever, and then run into problems (and don’t have a plan on how to recover), then I don’t have that much sympathy for you.
On the other hand, if you go through a thoughtful and thorough testing process, and you have a plan for how you will install the CU, and how you would recover if there were any problems, then you are much less likely to have any problems. You are also much more likely to avoid the issues that are fixed by all of the included fixes in the new build of SQL Server. You have done your job as a good DBA.