![]() |
|
![]() |
![]() |
Archives of the TeradataForumMessage Posted: Mon, 09 Jun 2003 @ 19:45:02 GMT
...That is the question. Ok, so I am forgetting my Teradata 101...I would like to ask the group if there are any drawbacks to creating an index to cover a set query. My example: I have a couple of tables which are both created with a column (ID) as the primary index...and this is the same column where my joins occur. If I run my query against these two tables 2.6Mil x 78000 rows, it takes around 31 minutes to complete. If I run create index (ID) order by Hash (ID) on < As you can see, the savings is substantial, but the question is...at what cost. Would a query not using the (ID) column suffer? Or is the cost merely storage and maintenace of stats on the new index? Thank you for the Teradata 101 refresher.
| ||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||