In planning a resource limit, consider:
When to impose the limit (times of day and days of the week)
Which users and applications to monitor
What type of limit to impose
I/O cost (estimated or actual) for queries that may require large numbers of logical and physical reads
Row count for queries that may return large result sets
Elapsed time for queries that may take a long time to complete either because of their own complexity or because of external factors such as server load
Whether to apply a limit to individual queries or to specify a broader scope (query batch or transaction)
Whether to enforce the I/O cost limits prior to or during execution
What action to take when the limit is exceeded (issue a warning, abort the query batch or transaction, or kill the session)
After completing the planning, use system procedures to:
Specify times for imposing the limit by creating a named time range using sp_add_time_range
Create new resource limits using sp_add_resource_limit
Obtain information about existing resource limits using sp_help_resource_limit
Modify time ranges and resource limits using sp_modify_time_range and sp_modify_resource_limit, respectively
Drop time ranges and resource limits using sp_drop_time_range and sp_drop_resource_limit, respectively
