tune-workloads

You can fix Teradata query misclassification by autonomously analyzing and adjusting workload classification rules, filters, and priorities. This Skill adds or modifies criteria to ensure queries route correctly, directly addressing performance degradation and unmet SLAs.

You can autonomously configure Teradata workload management by using MCP tools to analyze and adjust workload definitions. This process involves adding or modifying classification criteria, leveraging predefined templates, and verifying changes for improved routing.

Yes, you can add fine-grained sub-criteria like MINSTEPTIME and FTSCAN to Teradata workload filters. This provides precise management of query execution time and scan types to ensure accurate classification within your workload rulesets.

The best way to route critical ETL queries is to add a new classification rule to the appropriate filter, such as matching the ETL_LOADER application within an ETL_FILTER. This ensures they are correctly routed to improve ETL job performance.

Yes, workload classification adjustment uses predefined templates for common classification patterns based on application, user, or query complexity. This template-driven configuration streamlines the process of adding or modifying rules.

Teradata database queries are often misclassified when existing workload rulesets lack the necessary criteria to distinguish them. Autonomously adding sub-criteria like FTSCAN or MINSTEPTIME resolves this by enabling finer query distinction and proper routing.