Release Service Pack 2 for SQL Server 2012 - by Erland Sommarskog

Status : 

 


309
0
Sign in
to vote
ID 814656 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 1/24/2014 12:37:40 PM
Access Restriction Public

Description

Service Pack 1 for SQL 2012 was released over a year ago. Since then, numerous bugs have been fixed. They are available in cumulative update packages (10 to date). However, Microsoft recommends customers not to install these cumulative updates unless affected by one of the fixed bugs. That creates a dilemma for SQL Server administrators. You do not want to install a package if Microsoft recommends against it, but you also want to take pro-active action so that you can squash the bug BEFORE it affects you. 
Sign in to post a comment.
Posted by MarkTab marktab.net on 11/23/2014 at 12:39 PM
Test
Posted by AaronBertrand on 11/22/2014 at 2:41 PM
Can I comment on Erland's SQL Server items? I think so...
Posted by Microsoft on 6/10/2014 at 10:30 PM
Hi all,

SQL Server 2012 Service Pack 2 released today (http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/06/10/sql-server-2012-service-pack-2-sp2-rtm-has-released.aspx) I am resolving/archiving this item.

Regards
Jean-Yves Devant

Senior Program Manager
•Servicing PM of High Availability and Mobile Technologies in SQL Server.
•Feature PM for Replication Technologies.
•Business owner, release PM and project manager of Service Packs for SQL Server.
Posted by Microsoft on 6/10/2014 at 10:30 PM
Hi all,

SQL Server 2012 Service Pack 2 released today (http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/06/10/sql-server-2012-service-pack-2-sp2-rtm-has-released.aspx) I am resolving/archiving this item.

Regards
Jean-Yves Devant

Senior Program Manager
•Servicing PM of High Availability and Mobile Technologies in SQL Server.
•Feature PM for Replication Technologies.
•Business owner, release PM and project manager of Service Packs for SQL Server.
Posted by Jon Morisi on 6/10/2014 at 10:33 AM
Is the announcement for Microsoft SQL Server 2012 Service Pack 2 (the latest service pack) legitimate? http://support.microsoft.com/kb/2755533#sp2

The links for the download appear to be broken.
Posted by JaySee on 4/9/2014 at 4:35 PM
Everything said above about CUs is especially true on government contracts. Please release Service Packs on a timely basis.
Posted by Microsoft on 2/13/2014 at 5:39 PM
Hi all,

I just wanted to let you know that I have posted an update on the SQL Release Services Blog (http://blogs.msdn.com/b/sqlreleaseservices/) to answer the feedback you are raising through this Connect item.
Thanks
Regards.

Jean-Yves Devant 
Senior Program Manager
Servicing PM of High Availability and Mobile Technologies in SQL Server.

Release PM of Service Packs for SQL Server.
Posted by Shanky_621 on 2/12/2014 at 6:12 AM
I agree with fact that Microsoft writes that CU's are meant to fix only particular anomalies and if you are not facing please dont apply.And this line seems to threated many customers and they become vary cautious .I agree to all post here that if possible please release Service packs for 2008,2008 R2 and 2012.Most required one is for 2012
Posted by yes please on 1/28/2014 at 3:18 PM
An official "release strategy" for SPs would be good also.
Posted by Andy_Mack on 1/28/2014 at 1:35 PM
A well consolodated SQL serfver can have dozens of applications using databases on it. To test them all for a patch can take weeks and cause considerable disruption to developement & testing cycles. Not to mention the cost. To do this for each CU is simply too expensive, especially when there isn't a specific problem to aim at. Servivce Packs can be justified to the business and cause less disruption.
Posted by SQLCHANTER on 1/28/2014 at 9:44 AM
It is quite surprising that even for premier support subscribers, the TAM does not bother to inform the current thinking or change in the offerings.
I concur with the view that a Service pack is in order for SQL 2012.
Posted by Papy Normand on 1/28/2014 at 9:11 AM
If a company wants to test all the novelties brought by a new version of SQL Server , it is a task needing at least 3 years and that is worst for small companies with a limited number of persons really able to perform these tests and to check whether an application will not be unable to work because of a change of behavior of a statement ( T-SQL or in Visual Studio applications ). Worst , I have the feeling that an error or improvement needed by the user is no longer provided in a SP but brought only with the next full version ( problem I am facing with Visual Studio already with 1 year between 2 versions ).
I think that Microsoft could consider to have to provide some respects towards the users of its products : 4 years between 2 versions ( a delay enough to provide a "good" version and to include the solution of all the problems appeared with the "main" version ).
I have decided not to "study" SQL Server 2014 because it is coming too quickly after the release of SQL Server 2012.Maybe I will use SQL Server 2016 but surely not a 2015 version ( I hope that the SQL Server Team will not do such an stupidity).
So , please , Microsoft : stop this ridiculous way to provide a new version every 2 years , and take the time to provide good versions as it was with SQL Server 2005 , 2008 and 2012 ( according to me , for most of little or middle companies , 2014 seems to be only a 2012 R2 as they are not implementing All Always ON and similar specifications , about Windows Azure , I am not sure that middle companies will use it ).
Most time the SQL Server Team will have to implement and to test fully new enhancements and improvements , less problems will be annoying for the users of SQL Server product ( and they will be glad and faithful to this product which is good.. ) and a glad customer is a customer who will advice his/her friends to buy Microsoft products ...
So 4 years between 2 full releases and at least 2 Service Packs , if you please ( or I will think that Microsoft wants to provide a new version every 2 years only to have more money , an enormous "marketing" error which could "sink" Microsoft )
Posted by WoodsBG on 1/28/2014 at 7:35 AM
Been waiting for SP2 for awhile. I have no confidence in CU's, I see too many of them cause too many problems. By the time the service pack is released these issues are all fixed. Please release SP2 for SQL 2012.
Posted by D. McCallie on 1/28/2014 at 5:35 AM
Please release service packs in a timely fashion - at least once per year!
Posted by Dan Guzman on 1/28/2014 at 4:33 AM
I believe most customers would like to see service packs released in a regular cadence, with the frequency depending on product maturity. That will better facilitate planning the associated testing and implementation cycles.
Posted by Dexter Jones on 1/28/2014 at 3:53 AM
With the increased cost of SQL Server 2012, it is a disservice to customers (and themselves) for Microsoft to not provide this minimal level of service for a flagship product.
Failing to do so does not enhance Microsoft's reputation in this space.
Put more bluntly, higher cost plus lower service is a very good recipe. For failure.
Posted by Koen Verbeeck on 1/27/2014 at 11:45 PM
I agree. There are very important CUs, such as enabling Power View to work on Multidimensional SSAS.
I had to convince the current client to install the CU, while an SP would've probably been accepted without arguments.

Time for SP2!
Posted by TheSQLGuru on 1/27/2014 at 3:22 PM
I thought we were on "only" 8 CUs for SQL 2012 SP1, but regardless it is definitely time for SP2. There have been many INCREDIBLY important fixes since SP1 was released!
Posted by AndrewTuerk on 1/27/2014 at 8:03 AM
Agreed. Most organizations I have seen build their testing cycles around SP, not CU. After a full year it is time to get SP2 out the door so the benefits of each fix can be felt by those who need to wait for a SP.
Posted by Uwe Ricken on 1/27/2014 at 5:53 AM
Due to reservation to CU's many customers refuse the Installation of CU's. Additional problem for this point is the warning of Microsoft itself to install CU's. The result are many companies / customers running old builds of SQL Server.
Posted by pmpjr on 1/24/2014 at 1:30 PM
Agreed. Guidance from Microsoft, either by changing the messaging around CU installations, or by releasing SP2 would be appreciated.