Priorities are a set of usage restrictions imposed on an AuthID. Setting priorities gives an XDB Server Administrator the ability to define XDB Server usage priorities for peak hour processing, or to restrict users who do particularly intensive queries to off-peak hours.
You control a user's access to an XDB Server by defining a priority (a set of usage restrictions) and then assigning the priority to the user's AuthID. An AuthID that exceeds any of the limits of it's assigned priority is disconnected from the XDB Server.
If you are not running against an XDB Server version that supports priorities, or if the XDB Server has the Governor feature turned off, the Priorities command is grayed out on the Admin menu.
A new or changed priority does not take effect until the XDB Server is shut down and restarted.
Priorities are defined through the Define Priority dialog box. Priorities can be defined to limit users by number of API calls, amount of time in the XDB Server SQL engine, amount of time processing calls, amount of idle time and/or the number of fetches. You can also set the times of the day when these limits are in effect.
All the limits set for a priority are checked by the Governor on the XDB Server. Using the Server Configuration utility, you set the MAXIMUM GOVERNOR CYCLE TIME to define how often the governor checks whether a user has exceeded priority limits. To turn off the XDB Server Governor, set this cycle time to zero. Because the frequency with which the governor checks the user's limit status is not infinitely small, it is possible for the limits to be slightly exceeded before the governor takes action. For more information about the Governor features of the XDB Server, see the description of the Maximum Governor Cycle Time option in the section Governor Cycle Timein the chapter Server Configuration Utility in your SQL Option Server Administration Guide.