Archives of the TeradataForum
Message Posted: Thu, 24 Mar 2011 @ 14:57:07 GMT
Table looks compact and compressed, which is good.
Next step is analyze the queries hitting the table.
Do most queries qualify on date range? I don't see a date dimension in the table, other than load_time. Many event tables partition by date, and then may have a second-level partition on another field, such as event code.
If you're getting a lot of joins on non-PI columns, Teradata may have to redistribute, which could be very expensive. A covering single-table join index on common column(s) used to join to other tables might be helpful, if you have the disk space.
Aggregate join indexes, or even summary tables, might be considered if you find query patterns where users are frequently summarizing data by GL Account ID, or other fields.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|