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

Using query band


Teradata Database provides an intelligent way to tag and track your request when they are in Database. When there are several users executing queries on the system using multiple applications, it becomes important to keep track of the requests in Database. By using Viewpoint, you can view the request status, but to track its resource consumption you require another mechanism. Let's understand query band with an example:

Suppose you have an ETLoad job for an application, and you want to track and analyze the execution of jobs so that if something goes wrong with a job, you know when, what, and where it happened. To make it happen you are required to create a log table where all the activity of the job is recorded. Usually, you would need to log all the steps of your ETL process, and in the logs you would specify unique Load ID, Process ID, Step ID, and so on. You do this because you want to understand which specific request caused performance degradation or failed, and without...