Archives of the TeradataForum

Message Posted: Wed, 10 Mar 2004 @ 15:16:00 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I don't know why it works that way, but that's the way it works (and it IS agonizingly slow). My experience, on an early release of V2R5.0 (say about .11, but don't hold me to that), was that defining the table without the NO RANGE partition did not produce the "Partition error..." you mention.

BTW, when I EXPLAINed the "alter table... drop range..." sql statement, it showed the inserts and deletes. Of course I did that after running the sql, violating one of my rules about explaining sql, especially "new" sql. :>)

If you want to delete the rows and drop the partition, first delete the rows explicitly; that should go pretty quickly. Then drop the partition, and taht will go very quickly.

Don Stubbs
Teradata Advanced Certified Professional

	<Prev	Next>		<<First	<Prev	Next>	Last>>