Performance problem
-
Hi Currently we are using crystal report to display the data whihc is internally fetching almost 55,234,22 records from DB. Since it the no of records are huge it is taking almost 7 minutes to display the report which is very poor performance in nature. Can anyone suggest me some useful sites to make it faster and can recommend some free tool to measure the exact point which is causing the issue? Thanks & Regards, SMA
-
Hi Currently we are using crystal report to display the data whihc is internally fetching almost 55,234,22 records from DB. Since it the no of records are huge it is taking almost 7 minutes to display the report which is very poor performance in nature. Can anyone suggest me some useful sites to make it faster and can recommend some free tool to measure the exact point which is causing the issue? Thanks & Regards, SMA
sma123# wrote:
Since it the no of records are huge it is taking almost 7 minutes to display the report which is very poor performance in nature.
Stop right there; that is not poor performance. Something taking a lot of time does not mean that it does not perform. What's the size of a single record? Just use Google to look up the size of each field that has no length. Now multiply that by the amount of records. Now take into consideration that it is a Crystal Report, not some text-only output. You could start with pasting the query here; you'd also want to download a profiler for Sql, and/or use SQL Management Studio to see if you can optimize the query. That's the fetching-the-data part. The other part would be getting the fetched data into a report-format. If you do not need all the fancy stuff that CR provides, then try writing a simple HTML-report.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Hi Currently we are using crystal report to display the data whihc is internally fetching almost 55,234,22 records from DB. Since it the no of records are huge it is taking almost 7 minutes to display the report which is very poor performance in nature. Can anyone suggest me some useful sites to make it faster and can recommend some free tool to measure the exact point which is causing the issue? Thanks & Regards, SMA
I agree with Eddy, this is not a performance problem, seems more like a poor implementation of user requirements. Am I correct in understanding that the report fetches 55 million records, but does it display that much data ? Displaying 55 detail records per page would generate a 1 million page report. Really ? Does the user need to see all of that data ? Is there any way to create summary data at an off-peak time so the report can generate from that summary data ? What about implementing an asynchronous report generator where the user selects the input parameters, then "kicks off" the report in the background. The report could generate an HTML or PDF report, then send an email to the requestor with a hyperlink to the report when it is complete. You would be surprised how agreeable a user would be to a solution like this. They kick off a report, then they can move on to something else while it generates. The email tells them when it is done. Hope these ideas help. :)
-
I agree with Eddy, this is not a performance problem, seems more like a poor implementation of user requirements. Am I correct in understanding that the report fetches 55 million records, but does it display that much data ? Displaying 55 detail records per page would generate a 1 million page report. Really ? Does the user need to see all of that data ? Is there any way to create summary data at an off-peak time so the report can generate from that summary data ? What about implementing an asynchronous report generator where the user selects the input parameters, then "kicks off" the report in the background. The report could generate an HTML or PDF report, then send an email to the requestor with a hyperlink to the report when it is complete. You would be surprised how agreeable a user would be to a solution like this. They kick off a report, then they can move on to something else while it generates. The email tells them when it is done. Hope these ideas help. :)
Agree. Only one thing: its 55 laks (5.5 million) of records, not 55 million. Those Indian data formats are so nice!
-
Hi Currently we are using crystal report to display the data whihc is internally fetching almost 55,234,22 records from DB. Since it the no of records are huge it is taking almost 7 minutes to display the report which is very poor performance in nature. Can anyone suggest me some useful sites to make it faster and can recommend some free tool to measure the exact point which is causing the issue? Thanks & Regards, SMA
That is not a report it is a data dump and should not be produced via a reporting tool. Dump the data via CSV direct to the hard drive and give it to the user unformatted. As suggested, this is a lousy implementation of the user requirements, go back and find out what the user wants with that many records.
Never underestimate the power of human stupidity RAH
-
I agree with Eddy, this is not a performance problem, seems more like a poor implementation of user requirements. Am I correct in understanding that the report fetches 55 million records, but does it display that much data ? Displaying 55 detail records per page would generate a 1 million page report. Really ? Does the user need to see all of that data ? Is there any way to create summary data at an off-peak time so the report can generate from that summary data ? What about implementing an asynchronous report generator where the user selects the input parameters, then "kicks off" the report in the background. The report could generate an HTML or PDF report, then send an email to the requestor with a hyperlink to the report when it is complete. You would be surprised how agreeable a user would be to a solution like this. They kick off a report, then they can move on to something else while it generates. The email tells them when it is done. Hope these ideas help. :)
David Mujica wrote:
I agree with Eddy, this is not a performance problem, seems more like a poor implementation of user requirements.
I think your answer is more correct however.
David Mujica wrote:
Really ? Does the user need to see all of that data ?
No user needs to see that. Even if they say they want to see it they in fact want to look something up and that is what one should do instead.
-
David Mujica wrote:
I agree with Eddy, this is not a performance problem, seems more like a poor implementation of user requirements.
I think your answer is more correct however.
David Mujica wrote:
Really ? Does the user need to see all of that data ?
No user needs to see that. Even if they say they want to see it they in fact want to look something up and that is what one should do instead.