FAQ

Q1: Can you please provide me with a "cheat sheet" on what changed with Teradata Priority Scheduler in V2R6?

A1: Here is a summary of the things that have changed with Teradata Priority Scheduler in the new release.

Several options/parameters have been removed, including:

• Internal Performance Groups
• Attributes such as Priority ON/OFF, I/O Prioritization and Throughput vs. Response
• The VALUE parameter of the performance group, which in Teradata Database V2R5 controlled ranking within a resource partition
• The allocation group POLICY (default, immediate, relative, absolute)
• The limit on the number of performance groups within one resource partition (was eight in Teradata Database V2R5)

New enhancements include:

• DBS-generated critical work has been disassociated from the default resource partition. This internal critical work now runs outside the user-controlled priorities as "system" work, meaning you no longer have to keep RP0 as the highest-weighted resource partition
• New allocation group parameter to limit CPU
• Default time quantum for UNIX is now 10 ms (was 20 ms)

In general, these changes simplify setup, but they have also caused some of the setup commands to use slightly different syntax. Because of that, you will need to modify any schmon scripts you use to change settings before attempting to run them on Teradata Database V2R6. Both allocation group and performance group definitions will need to accommodate the changes mentioned above. The release summary describes these required changes.

Teradata Priority Scheduler settings that are currently active will be automatically migrated to match the Teradata Database V2R6 syntax. If you are using Teradata Priority Scheduler Administrator (PSA), be aware that a PDSet is not converted until the user opens PSA and loads the PDSet. You must save the PDSet to the database in order to preserve the converted settings.

A Teradata Database V2R6 version of the Teradata Priority Scheduler Orange Book is being finalized and will be available sometime in the first half of 2005. T