Book Image

Teradata Cookbook

By : Abhinav Khandelwal, Viswanath Kasi, Rajsekhar Bhamidipati
Book Image

Teradata Cookbook

By: Abhinav Khandelwal, Viswanath Kasi, Rajsekhar Bhamidipati

Overview of this book

Teradata is an enterprise software company that develops and sells its eponymous relational database management system (RDBMS), which is considered to be a leading data warehousing solutions and provides data management solutions for analytics. This book will help you get all the practical information you need for the creation and implementation of your data warehousing solution using Teradata. The book begins with recipes on quickly setting up a development environment so you can work with different types of data structuring and manipulation function. You will tackle all problems related to efficient querying, stored procedure searching, and navigation techniques. Additionally, you’ll master various administrative tasks such as user and security management, workload management, high availability, performance tuning, and monitoring. This book is designed to take you through the best practices of performing the real daily tasks of a Teradata DBA, and will help you tackle any problem you might encounter in the process.
Table of Contents (19 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Identifying suspect queries


Daily, thousands of queries execute on a Teradata database. Some queries' execution is under milliseconds; these are quick and not visible in the monitoring portlet called viewpoint. Some queries have a tendency to execute over minutes, some execute over hours. Whatever the queries are, they need to consume resources on the system. Queries that consume resources such as CPU and IO in their threshold values are classified as good or optimal queries.

Queries that over consume the resources are called suspected queries. Analysis of these queries is necessary from time to time. If these are not inspected over time it can cause the system to under perform.

Definition of and classification of these suspect queries depends on the system. A Teradata database with high configurations such as a large number of nodes can withstand high resource queries for some time, but still these queries—irrespective of the system—are bad in nature and need to captured and tuned.

Getting...