Report slow when using WCS

[chewkp]

The report is fast when executed within the CR development environment - less than 30 seconds. It takes more than 10 minutes when executed in ASP via the WCS.
We have done the following investigations:
a) run in CR v 8.0 and 8.5 with the same slow response time.
b) run the stored procedure in SQL server and it takes less than 10 seconds.
c) confirmed that the parameters passed from ASP to the CR via WCS to the stored procedue is correct.
d) the result recordset from executing the stored procedure directly and from via the ASP is the same.
e) the initial report is a crosstab. We modified it to a simple list of the result recordset and the response time is still slow.

 

[pgtek]

hi

try to create a view from your your store procedure or a crystal query that would populate the information in the view or crystal query and save your report with data. If the data does not change and no user requirement is need to run this report. then run your report and save with data and then when the report is generated thru ASP it will popup faster since the data is in the report
I had that problem when i was using Ingres database

cheer

pgtek

 

[chewkp]

What I do not understand is that why running the same CR report via WCS is so much slower than running it directly in the CR development environment?

 

[pgtek]

hI
Well if your using ASP pages you will see it has to build its query first before passing it to the report.
it has to read your query then pass it and then get the result back and posted to the web pages.
you can speedup the process by saving with data. All report running asp apges thru the web are slow except the one with save data
How many tables you have in your report?

pgtek

 

[chewkp]

Hi,
If that is all that CR has to do, then, the extra 10 minutes makes the CR's WCS pretty inefficient when it takes 10 seconds to retrieve the data from the SQL server!
There are a few tables in the stored procedure. The point is that running the stored procedure with the same parameter in the SQL Query Analyzer takes less than 10 seconds, when the CR report is executed from the CR development environment it takes less than 10 seconds as well. When it is run from the ASP via the WCS, it takes 10 minutes!
So, unless my colleague has used the WCS incorrectly, my conclusion is that the overhead in running the CR report via the WCS is way too much.