× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yeah, Mike, there is a lot of space management and all that is done for us on the i - there are lots of knobs in DB2 for LUW that need to be set, to optimize performance.

I haven't worked in those myself but did work alongside a fellow who did, when testing the new query engine in 2001 - he said there's a lot to do for that version.

Cheers
Vern

On 1/13/2016 4:06 PM, Mike Jones wrote:
>From a developer perspective I tend to agree with Joe. Although, I'd be
willing to bet that DB2 LUW has a larger development budget than the DB2
for i team.

>From an administrator perspective, DB2 LUW, at a glance, looks like it
needs a lot more baby sitting and administration.

Mike


date: Wed, 13 Jan 2016 15:14:10 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: DB2 vs MySQL ... Oh I have learned a lot!

Hi Joe

There are some things that IBM i got first - so we're not so much the
redheaded stepchild anymore. It was something recent - maybe
row-column-access-control - I forget at the moment.

Vern

On 1/13/2016 12:16 PM, Joe Pluta wrote:
-snip-

Me, I'm more upset that DB2 LUW always outpaces DB2 for i, but I've
learned to live with being the last one at the table. Even a slightly
backward version of DB2 is indeed one heck of a powerful engine, and
there's absolutely nothing in the industry like the embedded RPG
integration.

In my (not so) humble opinion, of course. :)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.