SQL Reporting Services Timeout?

[malfster]

Hi, we have SQL Reporting Services Enterprise Ed. SP1 installed on a 2 server web farm with a SQL 2000 back end server (SQL SP4). All servers are Windows 2003.

We are having a problem - if we run a complex report that exceeds the timeout value specified in Report Manager (1800 seconds) the report is timed out from a user perspective, but SQL carries on processing the report in the background. In some cases we suspect the processing may have been running for days leading to application performance problems.

My question is - how can we configure SQL so it times out at the same time Report Manager times out? I would have thought that Report Manager would have forced SQL to time out but this doesn't seem to be the case.

TIA

Alastair

 

[Catadmin]

I don't know how you can link the two, but you should be able to set an independent timeout on SQL Server itself in the Server Properties.



Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???

 

[malfster]

OK thanks, will check this out.

 

[ookete]

wow, that is strange. Hmmm...

I know you can set a remote query timeout property in Enterprise Manager (right click your server name -> Properties -> Connections tab -> fill in the Timeout box near the bottom). This is for remote connections. Is your report server local to your SQL?

Still, I am not sure you want to enforce the same timeout rules across the board as you do with Reporting Services reports. Perhaps there are some settings you can mess with elsewhere. I will let you know if I find anything.