Many of the performance issues may be related to database design
and the complexity of the request.
One of the earlier posts asked how long it took to process
(some huge number) of records...
I don't think IBM has ever represented QU2 as anything more than
a query tool using the newer sql engine and having many more presentation options than QU1. I hope someone buying this didn't think sql just got faster!
I do think this tool on the i will make many shops (including me) go back and study the proper concepts of data warehousing. Interactive queries should never be reading huge amounts of data, and we have years of postings of how to limit users from doing that, and better design database and indexes.
Jim Franz

----- Original Message ----- From: "Bryan Dietz" <bdietz400@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, October 16, 2007 3:10 PM
Subject: Re: Install 5733-QU2 on a barebones Model 515 and NLS woes

"You can overcome slow(ing) programs with faster hardware"
Bryan Dietz

Paul Nelson said the following on 10/16/2007 2:56 PM:
IBM doesn't have the ability to make any changes to a product they don't
own. If they had wanted to do it right, they should have told IBI to make it
a screamer product on the small boxes, and they wouldn't have to worry about
performance on the big ones.

On the other hand, IBM is a hardware manufacturing and sales company.
Perhaps they saw this as a way to generate hardware sales.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].