Archives of the TeradataForum

Message Posted: Wed, 16 Apr 2003 @ 14:07:59 GMT

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

Another thing, I think has some value on this issue is that in early days of our warehouse we FASTLOAD 'd or used an MLOAD and deleted all the rows when we resync 'd our master type tables daily, weekly or whatever.

Because the warehouse tables seam to grow in retention, ie 1 year, 2 years etc, these masters should never experience a delete ie you need to decode what something was for 2 3 4 5 or more years ago so ,,,,,,,,

So, when your source file is a full replace type file, we simply replace everything with an MLOAD (Don't Delete all the rows) and any missing rows on your source file stay in the table and each current row is replaced. This actually runs faster and Master Decode type tables don't experience a lock as may happen with a FASTLOAD nor do they encounter a partial table as may on occasion happen during a moment or two with a resync type MLOAD or a Fastload.

Todd's comment several days ago, about Lock For Access is a key thing also. That plus the 4.1 changes to prevent locking on index builds and we no longer have any issues at all that involve ""DISCONNECT During LOADS""..

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