Migration from 10.2B to 11.3

S

Stuart Tinto

New Member
Hi Guys,

I was wondering if any of you could help me out.

I have been tasked with finding out key benefits relating to doing an upgrade from 10.2B to 11.3 so that we can persuade some of our clients to upgrade to 11.3 as we need to justify them laying out the cash.

Cheers
Stuart
 
It is as simple as that: You don't wanna run any production system on an outdated software release. If you are reluctant to migrate to the new release of a software you will end up being unsupported and fighting bugs that have been fixed for a long time. Or even worse, you might hit a limit that has been lifted in a newer release and your database goes down and you can't fix it withouth a migration. If that happens, then you need to perform the migration at the time this happens to you and will take as long as it takes and your production system will be offline for that amount of time.

Just think about how much data growth there has been just over the last 5 years where the amount of data applications need to handle seemingly exploded. Plus, availability requirements, the service level agreement you need to fullfill with your application, have gone up dramatically.

The life-cycle of OpenEdge 10 is now more than 10 years ( the first OpenEdge 10 release was introduced 2002/2003 if I am correct ). Although it has evolved it is still a 10 year old software regarding concepts and architecture.

Plus you will miss a lot of improvements and features that you can use out-of-the-box just be migrating your database and re-compiling your application.

Heavy Regards, RealHeavyDude.
 
It's a free upgrade, but it's not free... ;) Testing and implementation cost money. Even if the actual work isn't terribly difficult, many companies will treat this like a full-blown project: PMs, charters, plans, etc. etc. And those people often aren't adept at judging the real risk of an activity like this so their knee-jerk reaction is to take the conservative (read: expensive) route.

To be clear I'm not opposed to it at all; there is definitely value in upgrading. 10.2B will receive no more features or, so we're told, service packs. It will also receive no more performance enhancements. The RDBMS Engine Crew has an established history of not only delivering new functionality with each point release but also easing limitations, increasing flexibility and availability, and tweaking algorithms and parameter defaults for better performance. Also, you will have much-improved tools to work with.

From a deployment perspective I consider 10.2B to 11.3 to be a low-risk upgrade. If I were you I'd focus at least as much attention to the development side. Particularly if you aren't yet developing in Eclipse, this upgrade is probably a bigger change for your developers than for your clients. This upgrade brings a lot of potential changes for devs both in the language and in the tools.
 
You can stay with the beloved OpenEdge Studio ( AppBuilder ) developer license if you want to - probably forever. From that point of view, there is absoluetly no change in the development environment. Of course, staying with AppBuilder, you won't benefit from the Eclipsed-based development environment - especially when you want to develop OOABL and/or for the .NET UI.

Heavy Regards, RealHeavyDude.
 
Certainly, you can stay where you are with the tools and write the code you've always written. They'll never go away. But as the platform evolves this may be an increasingly untenable position as your tools will remain frozen in time. New capabilities will only be added to the current tool set (PDSOE).

Or, if you don't care for IDEs, you could skip PSC tools altogether and code in emacs. :D
 
I'm not quite as keen on upgrades as the other folks here, only because they are stupendously costly (in terms of manpower etc., not Progress costs), often for the valid but hard to immediately quantify benefits that HRD mentions. But at the end of the day, it's like the dentist: unpleasant and costly, but better to do it than not, in the long run.

Anyway, we run both and the main difference I personally perceive is in the area of support for REST, XML, JSON. REST and JSON I believe is absent in 10; I think XML is there, but with some issues compared to 11. Don't quote me on this ;)
 
You must log in or register to reply here.
Back
Top