| Optimizing data retrieval in BIRT [message #252465] |
Tue, 14 August 2007 23:28 |
Eclipse User |
|
|
|
Originally posted by: jeremydorall.myway.com
Hello everyone,
To my understanding, whenever we send a sql query to the BIRT engine, it
will process the query, gather the data, render the report and finally
perform pagination. This works fine if the data that i'm retrieving is
relatively small.
But what if we have a substantially large amount of data to process? This
is the problem that i'm facing right now. Currently, the table that i'm
querying contains over 2 million records. And sometimes, some of the users
will issue queries such as "select * from table_a" which will obviously
take a long time to process. So im wondering right now if there is a
function in BIRT to limit the number of records returned for each page in
the report.
I know that for phpmyadmin, if we actually issued a query such as "select
* from table_a", it will limit the number of records returned for each
page(eg: 30 records). Then when the user proceeds to the next page in the
report, it will grab the subsequent 30 records. The result, is faster data
retrieval.
Are we able to do the same with BIRT?
thanks
|
|
|
Powered by
FUDForum. Page generated in 0.03482 seconds
Home