|
|
|
The set [no] rules option disables any rules that apply to statements executed during the session or to the tables affected by the statements. Existing rules as well as rules created during the session are disabled. To reenable rules, issue the set rules statement. By default, rules are enabled.
The set norules statement enables DBAs to turn off rules when necessary. For example, when using a utility that loads or unloads a database where tables can be modified from scripts and files prior to their processing by applications. To issue this statement, you must be the DBA of the database to which the session is connected.
Caution! After issuing the set norules statement, the DBMS Server does not enforce check and referential constraints on tables nor the check option for view.
|
|
|
The set printrules statement causes the DBMS Server to send a trace message to the application each time a rule is fired. This message identifies the rule and the associated database procedure that is invoked as a result of the rule's firing.
To disable rule-related trace messages, issue the set noprintrules statement. By default, rule-related trace messages are not displayed.
|
|
|
The set maxcost statement restricts the maximum cost per query on the database in terms of disk I/O and CPU usage. Value must be less than or equal to the session's value for query_cost_limit. When maxcost is set, it remains in effect until another set maxcost statement or the set nomaxcost statement is issued, or the session terminates. If a set nomaxcost statement is issued, the allowed cost of disk I/O and CPU usage becomes equivalent to the value enforced for query_cost_limit. If no query_cost_limit is set, there is no limit on cost usage per query. To set query_cost_limit for a user, use the grant statement.
For more information, see query_cost_limit in the description of Grant (privilege).
|
|
|
The set maxcpu statement restricts the maximum CPU usage per query on the database. Value must be less than or equal to the session's value for query_cpu_limit. When maxcpu is set, it remains in effect until another set maxcpu statement or the set nomaxcpu statement is issued, or the session terminates. If a set nomaxcpu statement is issued, the allowed cpu usage becomes equivalent to the value enforced for query_cpu_limit. If no query_cpu_limit is set, there is no limit on cpu usage per query. To set query_cpu_limit for a user, use the grant statement.
For more information, see query_cpu_limit in the description of Grant (privilege).
|
|
|
The set maxio statement restricts the estimated number of I/O operations that can be used by each subsequent query to the value specified. Value must be less than or equal to the session's value for query_io_limit. When maxio is set, it remains in effect until another set maxio statement or the set nomaxio statement is issued, or the session terminates. If a set nomaxio statement is issued, the allowed number of I/O operations becomes equivalent to the value enforced for query_io_limit. If no query_io_limit is set, there is no limit on the amount of I/O performed.
To set query_io_limit for a user, use the grant statement. For more information, see Grant (privilege)
|
|
|
The set maxpage statement restricts the maximum number of pages per query on the database. Value must be less than or equal to the session's value for query_page_limit. When maxpage is set, it remains in effect until another set maxpage statement or the set nomaxpage Statement is issued, or the session terminates. If a set nomaxpage statement is issued, the allowed number of pages becomes equivalent to the value enforced for query_page_limit. If no query_page_limit is set, there is no limit on max page usage per query. To set query_page_limit for a user, use the grant statement.
|
|
|
The set maxquery statement is an alias for the set maxio statement. When maxquery is set, it remains in effect until another set maxquery or the set nomaxquery statement is issued, or the session terminates. If a set nomaxquery statement is issued, the allowed number of I/O operations becomes equivalent to the value enforced for query_io_limit. If no query_io_limit is set, there is no limit on the amount of I/O performed.
|
|
|
The set maxrow statement restricts the estimated number of rows that can be returned to the application by each subsequent query. Value must be less than or equal to the session's value for query_row_limit. When maxrow is set, it remains in effect until another set maxrow statement or the set nomaxrow statement is issued, or the session terminates. If a set nomaxrow statement is issued, the allowed number of rows returned becomes equivalent to the value enforced for query_row_limit. If no query_row_limit is set, there is no limit on the number of rows returned.
For more information, see query_row_limit in the description of Grant (privilege).
|
|
|
The set [no] maxidle option specifies whether a time limit is in force, and how long it is in seconds. The value entered must be less than that defined by the idle_time_limit session privilege.
For more information, see idle_time_limit in the description of Grant (privilege).
|
|
|
The set [no] maxconnect option specifies whether a current session connect time limit is in force, and how long it is in seconds. The value entered must be less than that defined by the connect_time_limit session privilege. Specifying nomaxconnect resets the connection time limit to its default. For details, see [No]Maxidle.