Archives of the TeradataForum

Message Posted: Tue, 08 Apr 2003 @ 16:51:52 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Tom Stanek is correct that the accountname will not change as a result of a change in priority due to reaching a priority scheduler resource milestone limit. This is because the performance group name (which is part of the account string) will not have changed.

What has changed when a milestone limit is reached is a level deeper, the allocation group that the performance group is pointing to for that particular session. As resource milestone limits (if they have been defined) are reached by the running session, the session will fall under the control of one or several different allocation groups, usually set up to have increasingly lower relative weights.

In V2R5, because the new Query milestone type makes the milestone functionality more appealing, it will be helpful to remember that the automatic movement of a query into a lower priority allocation group will be invisible to some of the surrounding pieces, such as AMPusage, PMON, or TDQM, that have awareness at the performance group level only.

Thanks, --Carrie Ballinger

	<Prev	Next>		<<First	<Prev	Next>	Last>>