|
Archives of the TeradataForumMessage Posted: Thu, 16 Aug 2007 @ 12:51:25 GMT
Martin - I have seen both of the approaches U cited used with success, and there are many more to boot. I have seen regularly scheduled jobs that migrate data from production to lower environments. In other cases the jobs are pre-built and run on demand. The data that is migrated may be an agreed upon set of tables that is available for reuse/refresh in the lower environment. Sometimes the data (per agreement) is determined by a relative date (eg. last 45 days). Here's another thought, as the developers step on each others toes, U may find yourself having to play referee. Referee duties may include scheduling, allocating scarce spool and perm space resources. Your organization needs to develop a philosophy on how to do this and what priorities are assigned to the tasks. Good luck. Rgrds, Bill Gregg
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||