Rank: Newbie
Groups: Registered
Joined: 10/27/2015(UTC) Posts: 0  Location: Bangalore
|
I am new to seal reports.
Am connecting to DB2 database (as ODBC connection) as par one of the posts on this site and trying to fetch records in the range of 25000, with 5 columns of data. Each time I try to do this I run into a different set of problem. Once it did not load any thing and application stood still, other times it loaded data but got stuck at processing and so on.
Am I over loading the application by trying to pull 25k records in one shoot. Are these kind of issues some thing that any one has come across?
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 12/20/2013(UTC) Posts: 1,209  Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
|
This is a classic issue for a reporting tool when you reach a huge number of records...and Seal does not keep part of the records on the server. It has no really sense to show 25000 lines to an end-user, the HTML document will be very big for your browser, and the JavaScript for sorting and filtering will take a lot of CPU.... Normally, we did performances tests till 5000 records. So I would say first to use aggregate functions in your SQL to let the database engine do the work. You can also check this post: https://sealreport.org/f...g=posts&t=93#post195And you might also check the ODBC driver properties of DB2, I experienced that with an Oracle ODBC driver: I had to configure the network packet size to have reasonable performances on huge queries. Good luck.
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 10/27/2015(UTC) Posts: 0 Location: Bangalore
|
Yes, it's true that it wouldn't make sense to show 25000 records at once to the user, but we do have a requirement where a huge number of records (around 15k, which are a days transaction) to be pulled up on the report. Was just checking the possible worst case scenario.
Also just to confirm my understand, the tool does not store any information on the server, It just pulls up all the records returned from the query and passes it on to the client and client side pagination takes place, Is that right?
Is there a option of server side pagination, where say a set of records are pulled up on the first hit and when user wants to see the next set, clicks on the next button and next set is retrieved by hitting the DB.
I probably am asking for too much, just want to know if it is possible.
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 12/20/2013(UTC) Posts: 1,209 Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
|
No there is no server pagination in the current version, this could be a feature request but I never really experienced that this feature is useful.
You can try to generate huge report in a file using output, CSV is the best format for this.
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 12/20/2013(UTC) Posts: 1,209 Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
|
Update: The 3.1 versions supports server side pagination....
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
