Adaptive Server logins: high-priority users

If you assign preferred execution attributes to a critical user and maintain default attributes for other users, Adaptive Server does what it can to execute all tasks associated with the high-priority user first.

In process mode, one result of scheduling is that when an engine does not find a task in its local run or a global run queue, it attempts to steal a task from another engine’s local run queue. Engines can steal only tasks that have a normal priority, and can never steal a high-priority task for high-priority users. If engine loads are not well-balanced, and the engines running high-priority tasks are heavily loaded, the task-stealing can lead to high-priority tasks being starved of CPU, which is opposite of the intended affect of scheduling, but a natural side effect.