New Configuration Parameters

SAP ASE 16.0 includes new configuration parameters.

enable utility lvl 0 scan wait

Summary Information
Default value 0
Range of values 0 (off), 1(on)
Status Dynamic
Display level Comprehensive
Required role System Administrator
Configuration group Application Functionality

Allows you to run alter table ... add | drop partition commands while Adaptive Server runs isolation level 0 scans.

Note: The default value for enable utility lvl 0 scan wait depends on the value to which enable functionality group is set. If you set enable functionality group to:
  • 0 – the default value for enable utility lvl 0 scan wait is 0
  • 1 – the default value for enable utility lvl 0 scan wait is 1
Note: However, if you set enable utility lvl 0 scan wait to 1, it uses a value of 1 regardless of what you set enable functionality group to. See enable functionality group.

(UNIX Only) max network peek depth

Summary Information
Default value 0
Range of values 0 – 2147483647
Status Dynamic
Display level Comprehensive
Required role System Administrator
Configuration group Network Communication

Specifies how many levels deep SAP ASE peeks into a connections operating system receive buffer for a pending cancel. For example, if a client sends a new command followed by a cancel before SAP ASE finishes processing the current command, SAP ASE peeks into the operating system's receive buffer to the depth specified by max network peek depth. If the cancel occurs within the specified depth, both the current command and the command preceding the cancel are discarded, and SAP ASE waits for the next command.

aggressive task stealing

Summary Information
Default value 1 (on)
Range of values 0 (off), 1 (on)
Status Dynamic
Display level Comprehensive
Required role System Administrator
Configuration group SQL Server Administration

Enabling aggressive task stealing sets the SAP ASE scheduler task stealing policy to aggressive.

enable large chunk elc

Summary Information
Default value 1 (on)
Range of values 0 (off), 1 (on)
Status Static
Display level Comprehensive
Required role System Administrator
Configuration group Meta-Data Caches

Enables large allocation in the engine local cache.

engine local cache percent

Summary Information
Default value 50
Range of values 0–100
Status Static
Display level Comprehensive
Required role System Administrator
Configuration group Meta-Data Caches

Allows you to modify the engine local cache as a percentage of procedure cache.

large allocation auto tune

Summary Information
Default value 1 (on)
Range of values 0 (off), 1 (on)
Status Static
Display level Comprehensive
Required role System Administrator
Configuration group Meta-Data Caches

Configures SAP ASE preallocate large amounts of memory for query execution, which reduces procedure cache contention.

threshold event max messages

Summary Information
Default value 0
Range of values 0–2147483647
Status Dynamic
Display level Comprehensive
Required role System Administrator
Configuration group Memory User, Monitoring

Determines the number of events SAP ASE stores in the monThresholdEvent table. Once the number of events in the monThresholdEvent monitoring table exceed this value, SAP ASE overwrites the oldest unread events with new events.

threshold event monitoring

Summary Information
Default value 0 (off)
Range of values 0 (off), 1 (on)
Status Dynamic
Display level Comprehensive
Required role System Administrator
Configuration group Monitoring

Enable or disables SAP ASE from recording threshold events.

user log cache queue size

Summary Information
Default value 1 (on)
Range of values 0 (off), 1 (on)
Status Static
Display level Comprehensive
Required role System Administrator
Configuration group User Environment
Determines whether a queueing strategy is used for logging. Setting user log cache queue size to:
  • 1 – enables queuing for user log caches. The user log cache is divided into multiple cachelets, the number of which is dependent on the value of user log cache size.
  • 0 – disables queuing for user log caches. The user log cache is not divided into multiple cachelets regardless of the value to which you set user log cache size.