"James" <James@discussions.microsoft.com> wrote in message
news:11D15332-D7BC-4694-A3BB-15EB8F428406@microsoft.com...
> In order to stop some occasional blocking issues could I set the "query
> execution time-out settings" to 30 seconds for example. I understand it
> will
> kill the queries that exceed 30 seconds, but I would rather have that then
> to
> have everyone "lockup". I also understand that blocking is caused by some
> ineffecient queries, however untill we identify the problematic queries I
> would like to kill the blocking automatically.
>
> Thanks for any help.
> James

"Arnie Rowland" wrote:

> Of course you can make such a change.
>
> Please recognize that several activities, including reporting, usually
> require longer running queries, and your proposed change may cause those
> other activities and reports to mal-function.
>
> Using Profiler, you should be able to identify the blocking queries
> relatively easily.
>
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
>
> "James" <James@discussions.microsoft.com> wrote in message
> news:11D15332-D7BC-4694-A3BB-15EB8F428406@microsoft.com...
> > In order to stop some occasional blocking issues could I set the "query
> > execution time-out settings" to 30 seconds for example. I understand it
> > will
> > kill the queries that exceed 30 seconds, but I would rather have that then
> > to
> > have everyone "lockup". I also understand that blocking is caused by some
> > ineffecient queries, however untill we identify the problematic queries I
> > would like to kill the blocking automatically.
> >
> > Thanks for any help.
> > James
>
>