Prev: test - sql
Next: Maintenance plan in sql server 2008 management studio
From: Raj on 1 Jun 2010 19:32
Our devs would like to stay on SQL 2005 all the way until 2014 or so.. They
believe they will retire the app by then. What should we keep them informed
about as far as the cons of that approach ?

I understand mainstream support comes to an end next year... and we can go
extended support ... What does that really mean ? Are they the same kind of
support from MS ? I understand they wont get the new features,etc.. and they
don't care.. So I'm looking at some potential operational/licensing/support
issues that we need to consider if we do decide to run with SQL 2005 for the
next 5 years or so...





From: Tom Cooper on 1 Jun 2010 23:45
The differences between mainstream and extended support is discussed at
http://support.microsoft.com/gp/lifepolicy. The dates for support timelines
for various products/versions can be found at
http://support.microsoft.com/gp/lifeselect (you'll find SQL 2005 by clicking
on More-Servers in the Server category. You are right, the final date for
mainstream support for SQL 2005 is April 12, 2011 and the final date for
extended support is April 12, 2016.

Tom

"Raj" <raj(a)hotmail.com> wrote in message
news:es4ywKeALHA.3880(a)TK2MSFTNGP04.phx.gbl...
> Our devs would like to stay on SQL 2005 all the way until 2014 or so..
> They believe they will retire the app by then. What should we keep them
> informed about as far as the cons of that approach ?
>
> I understand mainstream support comes to an end next year... and we can go
> extended support ... What does that really mean ? Are they the same kind
> of support from MS ? I understand they wont get the new features,etc.. and
> they don't care.. So I'm looking at some potential
> operational/licensing/support issues that we need to consider if we do
> decide to run with SQL 2005 for the next 5 years or so...
>
>
>
>
>

From: GS on 3 Jun 2010 18:54
may be off topic.
I believe we have heard that a particular app will retire by certain date.
however, look at the number legacy app out there people thought would be
obsolete but still in use., worse the horrendous effort spent in keeping
them running


"Raj" <raj(a)hotmail.com> wrote in message
news:es4ywKeALHA.3880(a)TK2MSFTNGP04.phx.gbl...
> Our devs would like to stay on SQL 2005 all the way until 2014 or so..
They
> believe they will retire the app by then. What should we keep them
informed
> about as far as the cons of that approach ?
>
> I understand mainstream support comes to an end next year... and we can go
> extended support ... What does that really mean ? Are they the same kind
of
> support from MS ? I understand they wont get the new features,etc.. and
they
> don't care.. So I'm looking at some potential
operational/licensing/support
> issues that we need to consider if we do decide to run with SQL 2005 for
the
> next 5 years or so...
>
>
>
>
>


From: Geoff Schaller on 4 Jun 2010 03:36
Raj,

What it really means is that it will cost you 10 times over the cost of
upgrading to SQL Server 2008 and whatever it is that comes out next. You
will want fixes for things long since fixed in later versions and will
struggle to find staff that can remember that far back as time goes
further forward (or worse... get stuck with 'old' staff that couldn't
keep up :-) ).

Irrespective of the success of 2005, 2008 has productivity benefits for
the developer and DBA and a whole new generation better reports. Reports
alone are worth the upgrade but there are other features (indexing,
compression, SSIS, agent management, cpu efficiency, ram management,
etc...)

Upgrading is cheap and simple. I am struggling to see why a company
would resist. It isn't a case of jumping every version as it lands
(although we like doing that) but you're talking about a decade. In
computing terms that is positively an eon.

Geoff Schaller
Software Objectives


"Raj" <raj(a)hotmail.com> wrote in message
news:es4ywKeALHA.3880(a)TK2MSFTNGP04.phx.gbl:

> Our devs would like to stay on SQL 2005 all the way until 2014 or so.. They
> believe they will retire the app by then. What should we keep them informed
> about as far as the cons of that approach ?
>
> I understand mainstream support comes to an end next year... and we can go
> extended support ... What does that really mean ? Are they the same kind of
> support from MS ? I understand they wont get the new features,etc.. and they
> don't care.. So I'm looking at some potential operational/licensing/support
> issues that we need to consider if we do decide to run with SQL 2005 for the
> next 5 years or so...

 | 
Pages: 1
Prev: test - sql
Next: Maintenance plan in sql server 2008 management studio