Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 10 Jun 2014 @ 23:10:09 GMT


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


Subj:   Re: Restrict updates during backup run
 
From:   Martin Barrow

Raf,

There are a couple of options here.

1) Online backups - I'd recommend a stop gap in processing for the checkpoints to be taken and make sure you consider the DB and DBC growth for capturing the data change. This will allows the non-select queries to take palce and still have a clean restore point.

2) TDWM - In your version, you could still delay all non-select queries - use a throttle and delay all DDL/DML Query characteristics, include a Request Source if you only want to restrict certain users, Include a Target if you only want to restrict on specific objects - you would need to have a backup state and only have the throttle active during the backup state.

This will delay non-select queries and prevent backup impact

3) Amend access rights before and after backups - though this would obviously force the non-select queries to fail.


Regards,

Martin Barrow



     
  <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: 15 Jun 2023