Archives of the TeradataForum

Message Posted: Sat, 16 Aug 2003 @ 13:48:26 GMT

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

If that's the ONLY archivie job you have, then no, it is not a good idea. Depending upon the size of your installtion, it may take a long time and create one large backup file that will be a nightmare to restore. In case you ever need to restore, remember restores take almost 1.5 times the time taken for archive.

Regular backup of the DBC is required to preserve all the system information and more. Typically, you should have DBC, any SYSADMINs and other system related databases in one database and all the application databases in other jobs. The best way is to split the archive by applications. That way they stay manageable and avoid any blocks when restoring. Even within an application, size of a particular table should be considered when deciding whether to archie at the database level or the table level.If there are tables that are huge, it may be a good idea to break them out. If you have a table in a database that is particularly large, archive the database, exclude that table and then rchive that table seperately.

Dictionary Archives will only arcive the DDL. They are good for macros, views, SPs and tables that can be easily recreated. Aggregate or data mart tables mostly fit this. Tables that take a long time to load or cannot be recreated are best archived at the database level.

You cannot combine Data & Dictionary archives, they have to be seperate.

Running too many archives at the same time will also affect the run times, so plan accordingly.

Raghav

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