Can someone explain what exactly the ‘Limit execution time To:’ parameter on the Controls tab mean? We have the limit set to 30 minutes, however, nothing happens after 30 minutes…the results appear in 50 minutes. Is this clock time or CPU time? When does it begin and end? Any information would be helpful.
I believe that the limit you impose via Designer is the time a query can be allowed to run for. So, for example, if it took 30 minutes to run but then 20 minutes to draw the data, that might explain it. Also, if you have joined or synchronised data providers the limit doesn’t work as you would expect. digpen provided some good insight on this very topic a while back.
According to the Supervisor guide, this is the limit after which the query is halted. The query is the SQL that is sent to the database. So, processing of the SQL is halted after that time, in your case, 30 minutes. As Nick indicated, this limit doesn’t affect processing the data, which includes any calculations at the report level.
Many DB’s will have a more sophisticated resource management suite available internally that you might also explore – for example in Oracle 9i you can set force queries running longer than so-many minutes to drop to a lower priority class, then after more minutes to drop to an even lower one. An external application is not going to match that kind of flexibility.
you didn’t specify your RDMS but this feature does not work in DB2. With DB2, you would have to set time with the Resource Limit Facility.
Anybody else? How do execution limits work on other platforms?
I know you guys are expert but sometimes we overlook simple things
Please go and check that in Supervisor what is your Limit Execution Time?
Incase you are checking your execution time in Designer and if there is different setting in Supervisor, the supervisor setting would override the designer setting.
Thanks, Scott. That might be it. In this case, it is a DB2 database we are running against. What is the Resource Limit Facility? Is that something in DB2?