|
Archives of the TeradataForumMessage Posted: Fri, 13 Dec 2002 @ 19:05:16 GMT
Karen, Common approaches to this are: -- find a time slot for each table where it is not being loaded and archive it during that time slot. -- for tables where you haven't got a big enough time slot as per above, use permanent journals on the relevant tables. Using the GROUP READ LOCK option on the ARCHIVE statement allows updates/inserts etc to run alongside the archive. -- don't archive them (seriously !). Either keep the input files and re-process or take regular exports of a chunk of the data, say one calendar month, and use Fastload as your 'restore' mechanism. Doubtless there are others but I've seen all of the above used, often in combination with each other. Cheers, Dave Ward Analytics Ltd: Information in motion (www.ward-analytics.com)
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||