Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 03 Apr 2012 @ 09:27:17 GMT

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

Subj:   Re: Backing up table before dropping
From:   Machha Narayan Rao Naidu

Hi James,

I guess the issue is with the failed fast load where developers frequently ask us to drop and recreate the table in this scenarion taking a backup copy of table structure and stats will be sufficient and that to we can store it for temporary basis and then reapply the stats once the table is recreated.

Apart from above scenarios i guess if devlopers are asking to drop the table then it implies the data in it is not of use any more thus we can relay on weekly backup or else we can have quick arcmain backup.

If developers want to drop a recreate the table with data then i don't think that means any thing but still in those scenario we can take the backup in database it self with some naming convention like _bkp and then drop the backup table once the source table is recreated and data is inserted back.

Having the same approach in PROD and DEV will be helpful but not necessary.

At last as Fred suggested we should have some sort of formal change control / signoff - especially before you deal with a Production table.



  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 23 Jun 2019