BOL has this
SET QUERY_GOVERNOR_COST_LIMIT
Overrides the currently configured value for the current connection.
Syntax
SET QUERY_GOVERNOR_COST_LIMIT value
Arguments
value
Is a numeric or integer value indicating if all queries are allowed to run
(value of 0) or if no queries are allowed to run with an estimated cost
greater than the specified nonzero value. If a numeric value is specified,
Microsoft® SQL Server™ truncates it to an integer.
Remarks
Using SET QUERY_GOVERNOR_COST_LIMIT applies to the current connection only
and lasts the duration of the current connection. Use the query governor cost
limit option of sp_configure to change the server-wide query governor cost
limit value. For more information about configuring this option, see
sp_configure and Setting Configuration Options.
The setting of SET QUERY_GOVERNOR_COST_LIMIT is set at execute or run time
and not at parse time.
Permissions
SET QUERY_GOVERNOR_COST_LIMIT permissions default to members of the sysadmin
fixed server role.
--
Regards
R.D
--Knowledge gets doubled when shared
[quoted text, click to view] "David Gugick" wrote:
> raghu veer wrote:
> > my mdf and ldf are in 1 drive only. i am facing query timeout problem
> > for this server which is mainly used for employees
> > if i separate ldf into another drive will there will be any perf
> > benefit can i add another log file
> > how to clean up my log file
>
> No way to know for sure given the limited amount of information.
> Assuming you do not have SQL tuning problems or CPU-related issues (not
> enough CPU or other services/applications using too much), then a drive
> change should be in order. It's always a good idea to separate data and
> log files.
>
> A query timeout occurs when you set a maximum limit for query execution
> in your code. Have you set a maximum timeout value? Make sure you roll
> back the transaction when the query times out.
>
>
> --
> David Gugick
> Quest Software
>
www.imceda.com >
www.quest.com >
