query_governor_cost_limit will not help.
This option will allow SQL Server to refuse to run a potentially greedy query
i.e. It's all or nothing - Not just slow it down.
The only configuration option I know of that may be of use
( and only then if you have SMP = multiple processors )
is setting "max degree of parallelism " to limit the query to fewer processors.
If your query has parts, you may be able to break it up using separate
transactions and "waitfor delay", or look at breaking the rows it processes at a time
up into batches ( using a more restrictive where clause ). I've found a sql agent
job running a query bit at a time, by incrementing "where clause" parameters kept in a
separate table, a useful technique.
"Tobbe" <tobias.hasslebrantsundit.se> wrote in message news:046301c33fcc$c6411c60$a001280aphx.gbl...> Hi,
> Can I set the maximum I/O and memory usage when executing
> an transaction. The queries I'm executing are taking all
> the Power it needs leaving nothing to our business system.
> I have several SQL statements which I would like to run
> during working hours not during night.
> I have looked at the SET QUERY_GOVERNOR_COST_LIMIT but
> can't see what it really does.