Following is a series of events that could take place in an Adaptive Server environment with the configuration described in this example:
A client logs in to Adaptive Server as “L1” using OLTP.
Adaptive Server determines that OLTP is EC1.
“L1”does not have an execution class, so Adaptive Server assigns the default class EC2. “L1”gets the characteristics defined by EC1 when it invokes OLTP.
If “L1”executes stored procedure sp_xyz, its priority remains unchanged while sp_xyz executes. During execution, “L1”has EC1 attributes throughout.
A client logs in to Adaptive Server as “L1” using isql.
Because isql is EC3, and the “L1”execution class is undefined, “L1”executes with EC3 characteristics. This means it runs at low priority and has affinity with the highest numbered engine (as long as there are multiple engines).
When “L1”executes sp_xyz, its priority is raised to high because the stored procedure is EC1.
A client logs in to Adaptive Server as “sa” using isql.
Adaptive Server determines the execution classes for both isql and the “sa”, using the precedence rule. Adaptive Server runs the System Administrator’s instance of isql with EC1 attributes. When the System Administrator executes sp_xyz, the priority does not change.
A client logs in to Adaptive Server as “L2” using isql.
Because both the application and login are EC3, there is no conflict. “L2” executes sp_xyz at high priority.
