Currently Teradata offers two products that address data synchronization directly, Teradata Replication Services (TRS) and Data Mover (TDM). TRS is a highly available option that deploys a 2PC when updates occur on tables with TRS defined on them. Data Mover is a Table copy or table shipping utility that uses Teradata utilities such as fastexport, bteq and ARC to do table copy, full and partial tables can be copied this is an ansynchronous operation, therefore the secondary system if more vulnerable to getting out of synch when certain primaryt system faluresw occur. SRDF/SRDA technology is not a viable option with the Teradata DBMS. In any design, I will content that a sound table shipping foundation must be in place to begin with for all tables. There will always some cases where the table need to be restored from either copy of the data. The table shipping options that companies such as ebay and Meijer have put in place are sound strategies. What other customers have put in a general purpose table shipping function between multiple systems. (it already needs to be there from PROD to DEV/TEST for debugging purposes). Besides making the method of replication invisible and optimized based on the customers preference, what do customers need in a data synchronization tool?