Hierarchy
⤷ BC-DB-INF (Application Component) Informix
⤷ STUI (Package) Informix Database Monitor
Basic Data
Data Element | MAXPDQPRIO |
Short Description | Max PDQ Priority |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SINT4_NOS | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | MAXPDQPRIO |
Medium | 15 | MAX_PDQPRIORITY |
Long | 0 | |
Heading | 0 |
Documentation
Definition
MAX_PDQPRIORITY limits the PDQ resources that the database server can allocate to any one DSS query. MAX_PDQPRIORITY is a factor that is used to scale the value of PDQ priority set by users. For example, suppose that the database administrator sets MAX_PDQPRIORITY to 80. If a user sets the PDQPRIORITY environment variable to 50 and then issues a query, the database server silently processes the query with a PDQ priority of 40.
MAX_PDQPRIORITY lets the database administrator run decision support concurrently with OLTP without a deterioration of OLTP performance. However, if MAX_PDQPRIORITY is too low, the performance of decision support queries can degrade.
MAX_PDQPRIORITY takes one of the following values and affects all user sessions.
Value - Description
0 - PDQ is turned off; DSS queries use no parallelism.
1 - The database server fetches data from fragmented tables in parallel (parallel scans) but uses no other form of parallelism.
100 - Use all available resources for processing queries in parallel.
<number> - The number is an integer number between 0 and 100 that indicates the percentage of the user requested PDQ resources that the database server actually allocates to the query. Resources include the memory, CPU, disk I/O, and scan threads.
History
Last changed by/on | SAP | 20041216 |
SAP Release Created in | 700 |