Thank u for all of your responses, i really apriciate it :)
My stored procedure populates and processing the data required for the report, and doesn't have begin tran or rollback tran.
If it's the nature of the Reporting Service, just to send the request to the database server (I'm using SQL Server 2008 also).. Is there any workaround, if the report aborted, then it will send some query back to the SQL Server (ie. kills the session at the SQL Server).. ?
Because I have some ghost sessions that are still running for hours and making the server slow, the CPU utilization is higher than normal.. Maybe because of the stored procedure processing is quite big also.
Let me explain the case :
For example I have report A that triggers the execution of Stored procedure SP-A.
SP-A itself when triggered and run directly at the SQL Server, it will cost 2 minutes before the result showed.
When I'm trying to view the report through SQL Server BI Development Studio, it will cost more than 2 mintues to show.
But when I tried to view the report through Reporting service web, it will get timeout after more than 30 minutes running.
After timeout, I got the ghost session still running at the SQL Server for hours (more than 6 hours)
Do you know why the execution for the reports is different depends on from which program I called the stored procedure ?
Pls help me to resolve this problem :)
Thank u :D
↧