Archives of the TeradataForum

Message Posted: Mon, 10 Jul 2006 @ 15:51:45 GMT

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

Martin,

Yes, it is the no range. You have two options.

1) drop the no range which may not be possible if you actually have data falling into this area.

2) Use Multiplied delete.

We use Multiload delete. This gets around having to make changes when NO RANGE is added and cleanups are not changed. You don't want to get into the situation where you try dropping the data and the no range exists. It takes a long time and uses Transisent Journal. Much safer to mutliload delete even though it takes a longer (when no range deos not exist).

I personally hate the use of NO RANGE. ETL should not allow 'unknown', bad or out of range. Also new ranges should be added before the data in those ranges get added.

Thanks,

Bob Diehl

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