Back-to-Back Version of SQL Server

Question

Post reply

Back-to-Back Version of SQL Server

Saurabh.D

Ten Centuries

Points: 1164
More actions
November 10, 2016 at 11:14 am

#322828

Hi,
Not Sure, right place to ask.
I am very new to SQL Server.
Why Microsoft release Back-to-Back version of SQL Server within short gap.
SQL Server 2012 release date 26-July-2012
SQL Server 2014 release date 18-March-2014
SQL Server 2016 release date 1-June-2016
whereas SQL Server 2008 release in August 2008
Is it part of Product Management or just another trick to increase license cost.
ThanksSaurabh.D

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

ryanbesko Default port Points: 1424 More actions · Answer 1

SQL Server 2008 - Released 11/6/2008

SQL Server 2008 R2 - Released 7/20/2010

I think you are forgetting the R2 version. Microsoft called it that instead of SQL Server 2010, but has since changed to calling them 2012,2014, 2016 and so forth. No changes in the new version cycle.

Eric M Russell SSC Guru Points: 125562 More actions · Answer 2

If you don't like the 2 year cycle of releases, you always just sit every other one out. However, I'd recommend v2016.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 3

Saurabh.D (11/10/2016)
Hi,
Not Sure, right place to ask.
I am very new to SQL Server.
Why Microsoft release Back-to-Back version of SQL Server within short gap.
SQL Server 2012 release date 26-July-2012
SQL Server 2014 release date 18-March-2014
SQL Server 2016 release date 1-June-2016
whereas SQL Server 2008 release in August 2008
Is it part of Product Management or just another trick to increase license cost.

You should ask Microsoft. 😉

To be fair, they've made a large number of improvements. Why shouldn't they get paid for it?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)