SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


No More Service Packs


No More Service Packs

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)

Group: Administrators
Points: 247371 Visits: 19791
Comments posted to this topic are about the item No More Service Packs

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Summer90
Summer90
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12801 Visits: 3899
It will certainly simply patching. I hope vendors take testing CUs more seriously than they do Service Packs now.
Eric M Russell
Eric M Russell
SSC-Forever
SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)

Group: General Forum Members
Points: 48001 Visits: 12256
I trust Microsoft, particularly the SQL Server team, to do this right and to do it for the right reasons. It's probably the best engineered software product in the world.


"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
Chris Harshman
Chris Harshman
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17812 Visits: 5306
I think this decision further demonstrates that Microsoft is out of touch with their customer's needs. Releasing a major version of their software in a year and a half, and doing monthly updates of it drives people like me nuts because it shows that the product is unstable. Businesses want things to work, and work right the first time, not eventually. If I propose this schedule to the rest of the folks here in my IT department they would laugh, there is no-one available to do monthly testing of these updates, it takes more of my time to manage all these updates, and it has to make the product more difficult long term for Microsoft to support.
Summer90
Summer90
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12801 Visits: 3899
Chris Harshman - Tuesday, October 3, 2017 8:33 AM
I think this decision further demonstrates that Microsoft is out of touch with their customer's needs. Releasing a major version of their software in a year and a half, and doing monthly updates of it drives people like me nuts because it shows that the product is unstable. Businesses want things to work, and work right the first time, not eventually. If I propose this schedule to the rest of the folks here in my IT department they would laugh, there is no-one available to do monthly testing of these updates, it takes more of my time to manage all these updates, and it has to make the product more difficult long term for Microsoft to support.

It appears that Microsoft is attempting to turn SQL Server into a Windows patch schedule methodology.

We will never be able to keep up with monthly or even every other month CU releases. Not to mention the fact that if it is a purchased application we have to wait for the vendor to certify it or risk losing support if an issue arises.
Chris Harshman
Chris Harshman
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17812 Visits: 5306
Summer90 - Tuesday, October 3, 2017 8:41 AM
It appears that Microsoft is attempting to turn SQL Server into a Windows patch schedule methodology.
We will never be able to keep up with monthly or even every other month CU releases. Not to mention the fact that if it is a purchased application we have to wait for the vendor to certify it or risk losing support if an issue arises.

And I guarantee that in many places Windows patches DO NOT get properly tested! People do silly things like applying the updates to a test server for a week and if no-one complains then it must be all good. I value my databases and the data within them too much to let that happen.

Steve Jones
Steve Jones
SSC Guru
SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)SSC Guru (247K reputation)

Group: Administrators
Points: 247371 Visits: 19791
Summer90 - Tuesday, October 3, 2017 6:02 AM
It will certainly simply patching. I hope vendors take testing CUs more seriously than they do Service Packs now.

They take SP testing seriously. There is a lot of testing. There's even more to test. I really think that SPs are out of band, a separate process that means extra steps and potentially a different testing stream. I used to prefer SPs, but I think at today's pace and the way that software is moving, a constant patching process makes sense.


Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
WayneS
WayneS
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: General Forum Members
Points: 36900 Visits: 10746
Another thing to keep in mind for SQL Server... most of the new features have been in place in Azure SQL Database for quite some time before making it to the on-premises versions. Meaning that it's been tested for a while before making it to those versions - which should mean fewer bugs in the on-premises versions.

@Summer90: You don't have to do monthly patches - just use whatever cycle that you're comfy with. If you find an issue that is fixed in a CU already, you can always do a special patch. You make a valid point about 3rd party software needing the vendors stamp of approval.
@Steve: I think that Summer90 was talking about 3rd party vendors, not Microsoft,

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
Links: For better assistance in answering your questions, How to ask a question, Performance Problems, Common date/time routines,
CROSS-TABS and PIVOT tables Part 1 & Part 2, Using APPLY Part 1 & Part 2, Splitting Delimited Strings

Eric M Russell
Eric M Russell
SSC-Forever
SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)SSC-Forever (48K reputation)

Group: General Forum Members
Points: 48001 Visits: 12256
I guess this an effort on the part of Microsoft product teams to better synchronize shared code bases, builds, and testing between SQL Server 2016/2017 and Azure SQL Database, which would be less branching and duplication of effort on their part going forward.


"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
mjh 45389
mjh 45389
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2278 Visits: 1770
Eric M Russell - Tuesday, October 3, 2017 10:45 AM
I guess this an effort on the part of Microsoft product teams to better synchronize shared code bases, builds, and testing between SQL Server 2016/2017 and Azure SQL Database, which would be less branching and duplication of effort on their part going forward.

Having recently reduced our main product from four branches to three I can see many advantages in this!

We are currently on SQL Server 2012 which is due SP4 any day now (although it seems a variable feast). I am quite wary of SPs after having had a major issue with an OS related one in the noughties!

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search