Modifying resource limits  Dropping resource limits

Chapter 1: Limiting Access to Server Resources

Examples of modifying a resource limit

This example changes the value of the resource limit that restricts elapsed time to all users of the payroll application during the tu_wed_7_10 time range. The limit value for elapsed time decreases to 90 seconds (from 120 seconds). The values for time of execution, action taken, and scope remain unchanged.

sp_modify_resource_limit NULL, payroll, tu_wed_7_10, elapsed_time, 90, null, null, 2

This example changes the action taken by the resource limit that restricts the row count of all ad hoc queries and applications run by “joe_user” during the saturday_night time range. The previous value for action was 3, which aborts the transaction when a query exceeds the specified row count. The new value is to 2, which aborts the query batch. The values for limit type, time of execution, and scope remain unchanged.

sp_modify_resource_limit joe_user, NULL, saturday_night, row_count, NULL, NULL, 2, NULL

Adaptive Server Enterprise provides resource limits to help System Administrators prevent queries and transactions from monopolizing server resources. Resource limits, however, are not fully specified until they are bound to a time range.

A resource limit is a set of parameters specified by a System Administrator to prevent an individual login or application from:

In Adaptive Server Enterprise version 12.5.3, when the System Administrator modifies a resource limit, all users logged in the session see the change, including the System Administrator.

See “Getting information on existing limits” for more information.





Copyright © 2005. Sybase Inc. All rights reserved. Dropping resource limits

View this book as PDF