News
Perth, Australia
+ (61) 417713124
prosolutions@gavinsoorma.com

4 Comments

David Mann
  • Mar 14 2011
Great technique... I have created multiple replicats which serviced different sets of tables in a trail but had never considered going to a more granular level. I am assuming this wouldn't necessarily work for all tables... like if transaction serialization needed to be guaranteed or if there were some other tables involved in the transaction that had FKs that would need to be reconciled on the target side.
Mohan Babu
  • Mar 14 2011
Will the use of "Range" function in one or more replicat processes on the target DB preserve parent/child foreign key constraints after all the replicat processes complete processing?
Gavin Soorma
  • Mar 15 2011
Hi Mohan - if you have tables related to each other like EMP and DEPT, the you will need to include both in the Extract or Replicat configuration when using the RANGE function - will try and do a test of this and send you the result
Gavin Soorma
  • Mar 15 2011
Hi David - if you have tables related to each other like EMP and DEPT, the you will need to include both in the Extract or Replicat configuration when using the RANGE function - will try and do a test of this and send you the result

Leave Reply

Your email address will not be published. Required fields are marked *