|
Archives of the TeradataForumMessage Posted: Fri, 23 Sep 2005 @ 14:26:18 GMT
Drop partitions should be almost instantaneous. If it takes a while, one of two things is happening. 1) The drop partition statement is blocked by a request using the table. 2) You have NO RANGE set on the table. If you drop the partitions with NO RANGE in place, it does not delete the data it moves them to the NO RANGE PARTITION. Only option I have found is to drop the NO RANGE PARTITION, DROP THE PARTITIONS then add back the NO RANGE. Personally I don't believe the NO RANGE option should be used. However, if the incoming data is not very reliable it might be necessary to have it turned on. However, better option is to prevent the bad data from getting loaded in the load process. I have not tested out the impact of Secondary indexes on a drop partition. This might also cause the drop partition to take much longer. Thanks, Bob Diehl
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||