timeout" and in Query Analyzer it can set the "Query time-out" option in
seconds.
My first question is:
Does the "remote query timeout" option only handle queries from remote
servers or does it work on queries directly conncected to the local SQL
Server? Meaning, does the "remote query timeout" option work like QA's
"Query time-out" on the server?
My next question is:
Depending on the answer from above, is there a way to configure the max
time for a given query?
The last question:
If SQL Server does not have a method for the above question, is there a
third party app that can limit the amount of time a query can take on
the SQL Server?
BillI think you have an option called CommandTimeOut in ADO. Using this, you can
set a limit in terms of the amount of time you want to wait for a query to
execute. If the time has elapsed, execution stops. You also have another
option called Query Governor Cost Limit, which determines uptil what cost a
query can execute. Every query has an execution cost and you can set a limit
on the maximum cost that is allowed for your application.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"William Enloe" <william.enloe@.domail.maricopa.edu> wrote in message
news:400476BF.B971E8F1@.domail.maricopa.edu...
quote:|||That may be true, but I don't have influence on the Development team
> SQL Server has (in its sp_configure) the option to set "remote query
> timeout" and in Query Analyzer it can set the "Query time-out" option in
> seconds.
> My first question is:
> Does the "remote query timeout" option only handle queries from remote
> servers or does it work on queries directly conncected to the local SQL
> Server? Meaning, does the "remote query timeout" option work like QA's
> "Query time-out" on the server?
> My next question is:
> Depending on the answer from above, is there a way to configure the max
> time for a given query?
> The last question:
> If SQL Server does not have a method for the above question, is there a
> third party app that can limit the amount of time a query can take on
> the SQL Server?
>
> Bill
because the fault was seen in Crystal. I've checked into the Query
Governor Cost Limit, but the cost (though documented in seconds) fails
to stop a query on a duration of time. In my test I set the Query cost
to 8 (seconds) and ran a simple (poor performance query) "Select * from
sysobjects A1, sysobjects A2". Though it is a cartesian product with a
runtime duration between 2 minutes to 8 minutes, the cost estimation in
query performance shows up as a 7. In my mind this query should never
run and I would never be allowed to govern the time a query takes if the
cost estimation isn't accurate to a closer number of the duration. So,
how is the cost derived and what can be done to limit query duration
from the server side?
Thank you,
Bill
SriSamp wrote:[QUOTE]
> I think you have an option called CommandTimeOut in ADO. Using this, you c
an
> set a limit in terms of the amount of time you want to wait for a query to
> execute. If the time has elapsed, execution stops. You also have another
> option called Query Governor Cost Limit, which determines uptil what cost
a
> query can execute. Every query has an execution cost and you can set a lim
it
> on the maximum cost that is allowed for your application.
> --
> HTH,
> SriSamp
> Please reply to the whole group only!
> http://www32.brinkster.com/srisamp
> "William Enloe" <william.enloe@.domail.maricopa.edu> wrote in message
> news:400476BF.B971E8F1@.domail.maricopa.edu...
No comments:
Post a Comment