During the month of April 2012 Microsoft released CU1 for SQL Server 2012.
Earlier I was focusing only on Service Packs (SP) whenever they are released. I moved on from this earlier strategy of ignoring CU’s.
I have decided to focus on CU’s too whenever they are released, and made up my mind to read/understand about the hot fix’s which are included in the CU.
Some of the fixes which are included in CU1 for SQL 2012 which grabbed my attention is mentioned below. You will need to refer to http://support.microsoft.com/kb/2679368 for the full list of fixes.
1. FIX: Low CPU spikes at a set interval even without user activity in SQL Server 2008 R2 or in SQL Server 2012.
This issue has got a very interesting symptom –
You have a huge database which has heaps and you have enabled Read Committed Snapshot Isolation (RCSI).You might experience low CPU spikes every 5 minutes without any user activity!
2. FIX: Backup fails in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 if you enable change tracking on the database
The symptoms for this issue are the backup will fail if the database is enabled for change tracking and the database has been recovered at least once after CDC was enabled.
I tried to repro this situation under RTM build, but never encountered this fix. In case you are getting this error for the above mentioned situation, then you can test out CU1.
3. FIX: It takes a long time to restore a database in SQL Server 2008 R2 or in SQL Server 2008 or in SQL 2012
The symptom of this issue is long duration for restoring databases which has many Virtual Log Files (VLF’s).
4.FIX: SQL Server Configuration Manager takes a long time to open if many SQL Server 2008 R2 or SQL Server 2012 instances are installed.
The symptom is Config Manager taking long time to open in case there are many instances configured on the same server. I don’t prefer running multiple instances for a real busy OTLP environment as sharing resources between the instances and management is a tough deal. These points are discussed well during initial phase of the planning itself.
The above mentioned lists of fixes are just the ones which grabbed my attention, as these issues might be common.
In case you are facing any issue and that issue has been fixed as per the KB article mentioned above, then you should test/validate CU1 and plan for deployment.The strategy of testing/deploying CU’s varies from environment to environment and this should be thoroughly discussed among the DBA team and well documented.