|
If you haven't done it already, you'll need to do some SQL performance tuning for the queries that Crystal Reports run on the server. This usually means building appropriate SQL indexes or when possible, changing the report itself so it does things smarter. Check this link out: http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzajq/rzajqkicko ff.htm especially "Creating an index strategy" sublink. As for ODBC data source, you could increase blocking factors and turn on caching. This will give you some benefit, but not nearly as much as server side SQL tuning will. Elvis -----Original Message----- Subject: Crystal Reports Access to Iseries We're at V5R3 and user is reporting via ODBC with C.R. version XI. His access was read/write which we changed to read only. Is there something else I can do to speed up his access? I'm testing EVI - anyone else using this? Thanks, Matt
As an Amazon Associate we earn from qualifying purchases.
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.