DbFlags
The following values are valid for the DbFlags parameter:
| Value | Description |
|---|---|
|
0 |
Enable the %UpdateStats meta-SQL construct. |
|
1 |
Disable the %UpdateStats meta-SQL construct. |
|
4 |
Disable a secondary database connection (used with the GetNextNumberWithGapsCommit PeopleCode function). This prevents the creation of a secondary database connection, bundling all SQL into a single unit of work. Without the additional database connection, the database row lock is held for a longer time, reducing concurrency in a multiple-user environment. Important: Analytic instance processing requires a secondary database connection, so if you're using analytic servers, ensure that this value is not set. In addition, the CallAppEngine PeopleCode function requires a secondary connection when used with the allowcommit parameter set to True. Therefore, ensure that this value is not set when using CallAppEngine with allowcommit set to True. |
|
8 |
Disables persistent secondary database connections (used by either the GetNextNumberWithGapsCommit PeopleCode function or the CallAppEngine PeopleCode function when the allowcommit parameter is set to True). When this value is specified, any secondary database connection created by GetNextNumberWithGapsCommit or by CallAppEngine is immediately closed after the commit completes execution. This keeps the number of database connections to a minimum, but requires each call to create a new secondary database connection on demand. Important: The performance impact of creating each new secondary database connection is significant, especially in high volume user production environments. Therefore, don't use this setting without carefully considering its effect. |
DbFlags uses a bit mask so that you can specify one or more of these values. You set this parameter to the total of the values that you want to apply. For example, to disable %UpdateStats and ignore the Truncate command, set DbFlags to 3 (setting bits one and two).
The default value is 0.