Archives of the TeradataForum
Message Posted: Fri, 23 Jul 1999 @ 16:01:07 GMT
John makes a good point regarding administration.
Like any OLTP environment, it's important to tightly manage your environment >if you have any hope of providing predictable response times. Some Teradata customers have used the user priorities in prior version to better allocate the resources of the system to OLTP activity. As I recall at KMART, the OLTP transactions used the $R (RUSH) priority to better ensure response time.
With the introduction of V2R3, the prioritization mechanism (Priority Scheduler) appears to be greatly enhanced, allowing for the creation of performance groups, assigned priority weightings, etc. Based on the documentation, it appears the this feature could help partition the eradata >environment and dedicate resources to particular system activity, like OLTP.
Has anyone taken advantage of the feature of the Priority Scheduler?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|