| # | Date | Where | Item | Comment |
|---|---|---|---|---|
| 4 | 14 Jul 2010 @ 11:12 PDT | carrie's blog | Collecting Stats on PARTITION for NON-PARTITIONED tables | I get it Carrie. Thanks a lot for clearing out my doubt! Thanks again.. |
| 3 | 12 Jul 2010 @ 12:05 PDT | carrie's blog | Collecting Stats on PARTITION for NON-PARTITIONED tables | Here are additional details - I partitioned the target table [DBNM.ERROR_TARGET] based on the numeric partition key of error code and collected Explain plan of a Insert query that inserts recor... |
| 2 | 12 Jul 2010 @ 11:30 PDT | carrie's blog | Collecting Stats on PARTITION for NON-PARTITIONED tables | Thanks for your detailed reply Carrie. We are not using the TPump functionality for our loads. We are performing loads onto the table in question via Informatica using Relational Connection that... |
| 1 | 08 Jul 2010 @ 10:00 PDT | carrie's blog | Collecting Stats on PARTITION for NON-PARTITIONED tables | Hello Carrie, I have been looking for answers to a basic question on table partitioning in Teradata. Can you please shed more light. Here it is - If we do Range Partitioning on a table based o... |