How Can I Use Filters to Prevent Poorly Written Queries from Reducing My Performance? - Teradata Viewpoint - Teradata Workload Management

Teradata® Viewpoint User Guide - 24.04

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Viewpoint
Teradata Workload Management
Release Number
24.04
Published
April 2024
Language
English (United States)
Last Update
2024-04-29
dita:mapPath
xwb1711972215358.ditamap
dita:ditavalPath
tky1501004671670.ditaval
dita:id
xvu1467243446040
Product Category
Analytical Ecosystem

A poorly written query can return too much data, making the results unusable. These types of queries often produce meaningless results, are very resource-intensive, and reduce the performance of your system.

Using filters, you can protect your system from poorly written queries by preventing these queries from even starting to execute. Rejecting bad queries also helps educate the users to write better and more specific queries, which can reduce the number of bad queries over time.

For information about how to write good queries, see the Teradata SQL documentation.

For example, you can prevent the following queries from executing:
  • Queries that return too many rows
  • Queries that take too long to run
  • Queries that scan very large tables

Scenario assumptions

This scenario assumes you already have the following set up:
  • Teradata Database version: 16.00
  • Operating system: SLES 11
  • System: PROD1
  • Ruleset: BadQueries