|
|
|
The set parallel statement controls the generation of parallel query plans by the optimizer. The optional degree of parallelism value indicates the number of exchange nodes (or points of concurrency) built into the plan. The default value is four. The set no parallel statement prevents the optimizer from creating parallel query plans.
Note: When tracing the I/O or the locks of a parallel query (using set io_trace or set lock_trace with set parallel n), the trace messages from child threads of the QEP are logged to the II_DBMS_LOG. The trace messages for the main thread are sent to the user session in the normal manner.
For a discussion of parallel query plans, see the Database Administrator Guide.
|
|
|
The set role option allows the session role to be changed during the life of the session using the set role statement, with the following syntax:
set role none | role [with password = 'role_password'']
If set role none is specified, the session has no active role. If set role role is specified, the current session role is set to the indicated role, if the user is authorized to use that role. Additionally, if the role has a password, that password must also be specified correctly using the with password clause. If either the user is not authorized to use the role, or the password is incorrectly specified, the session role is unchanged.
If a role has associated subject privileges or security audit attributes these are added to the maximum privilege set for the session when the role is activated, and removed from the privilege set when role is inactivated. Role security audit attributes can increase auditing over the current session value, but not decrease it.
|
|
|
The set [no]printdbevents option enables or disables display of event trace information for the application that raises events.
To enable the display of trace information, specify set printdbevents. To disable the display of trace information, specify set noprintdbevents. This option displays only events raised by the application issuing the set statement, and does not display events received by the application.
|
|
|
The set [no]logdbevents option enables or disables logging of event trace information for the application that raises events. When logging is enabled, event trace information is written to the installation log file. Specify set logdbevents to enable logging; specify set nologdbevents to disable logging. Only events raised by the application issuing the set statement are logged. Events received by the application are not logged.
|
|
|
This statement sets the beginning value for the random functions. There is a global seed value and local seed values. The global value is used until you issue "set random_seed," which changes the value of the local seed. Once changed, the local seed is used for the whole session. If you are using the global seed value, the seed is changed whenever a random function executes. This means that other users issuing random calls enhances the "randomness" of the returned value. Note that the seed value can be any integer.
If you omit the value, Ingres multiplies the process ID by the number of seconds past 1/1/1970 until now.