Typically, reporting scenarios require to aggregate one ore several facts of a certain reporting date or a range of dates.
If the involved tables are historized with start date and end date, the frequently seen join scenario is that the driving table is product joined with a calendar table and restricted on the reporting date, such as in our example below:
In today’s business, it is critical to respond as fast as possible to opportunities and problems as they happen.
These business events can be detected and collected for immediate processing resulting in an alert to a front-line user or an update message to an operational system.
Teradata parallel database triggers manage exactly this kind of live events.
Typically, every X minutes, a...
Updated 2015-07-07Teradata Comparison Operators and Performance are interrelated to some extent.
Choosing the proper comparison operator can make the difference between a well performing and a poor performing query.
But why should the selected comparison operators have an impact on performance?
Statistics are the most important input to the Teradata Optimizer, and they...
The Technical Details of the Non-Unique Secondary Index in Teradata - NUSI
Many concepts of Teradata indexing are tightly coupled to the physical storage of data rows. Therefore, I highly recommended reading our article series about physical storage: https://www.dwhpro.com/teradata-physical-storage/
The Teradata Non-Unique Secondary Index (NUSI) is an alternative data access path...
There are several ways of writing SQL statements and making use of transaction handling. Each method has its own advantages, disadvantages, and behavior which you have to consider.
As an example let's consider two statements which have to be executed in sequence:
(1) DELETE FROM TestTable;
(2) INSERT INTO TestTable SELECT *...
My mission is to make DWHPro a leading independent network for professionals working with Teradata from all walks of business life, across cultures, countries, employment statuses, industries or roles.