We are using Crystal Report 8.0, Sql Server 2000. All reports are launched from web server (asp code)
The Crystal Report 8.0 is installed in the Web server and some times the web server is slow when long running stored procedures are excecuted in the report. This creates a cascading effect and we are forced to restart the web server. We observed that this happens only if reports with long running query is fired.
Also if the user closes the report window even before the report is renderd then the web server is slow. We could see all stored procedures in the SQL Server 2000 (sp_who) piled up.
I suspect that Crystal Report is a single threaded and all requests are queued up. And if some user closes a window even before the report is rendered then all further report launched are slow and creating a cascade effect to slow down the web server (IIS).
The Crystal Report 8.0 is installed in the Web server and some times the web server is slow when long running stored procedures are excecuted in the report. This creates a cascading effect and we are forced to restart the web server. We observed that this happens only if reports with long running query is fired.
Also if the user closes the report window even before the report is renderd then the web server is slow. We could see all stored procedures in the SQL Server 2000 (sp_who) piled up.
I suspect that Crystal Report is a single threaded and all requests are queued up. And if some user closes a window even before the report is rendered then all further report launched are slow and creating a cascade effect to slow down the web server (IIS).