Re: Performance of ODBC vs. other access methods

I agree with you both (of course, I have to agree with my boss!) - Crystal's 
generated SELECT statements are generally dog-awful for access to iSeries data. 
The best technique is, I believe, to write your own statement in exact iSeries 
syntax as, what do they call it, pass-through or something. Then you are in 
control. And create the indexes you need.

-------------- Original message -------------- 
From: "Bill" <brobins3d@xxxxxxxxx> 

richard@xxxxxxxxxxx wrote: 

If you were asking about using iSeries ODBC from Crystal Reports to 
access DB2 I would tell you not to do it because it's butt-slow. 

Wow do I disagree with this! As with most any subject CR -can- be slow, 
but sometimes all it takes is an intelligent review of the generated SQL 
versus a review of the indexes and data involved and miraculous results can 
be achieved. I have personally made changes to reports that were 15 minute 
run times that are now less than 15 seconds. 

Bill 


-- 
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, 
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives 
at http://archive.midrange.com/midrange-l.