I think this is a good idea, as it can

JOSNA777

If we want to distinguish, there are two forms wizard type and draganddrop type. Draganddrop can be called data integration, because draganddrop focuses on data conversion and integration. The wizardstyle can be called data synchronization, because the wizardstyle focuses on data transmission and consistency. As for data collection, I rarely use it mixedly. I mainly understand it as collecting changes in the database. Again, this is entirely from a personal perspective. Handling during transportation In the process of data synchronization, does it need to be processed Although data synchronization is often compared with

ETL (extract, transform, load) but in fact it is It is debatable that Austria WhatsApp Number conversion is not required during synchronization. One to one synchronization The purpose of synchronizing data is to preserve the data history of the business. If you want to preserve the history, then the history of errors is also history. Therefore, this kind of synchronization is completely onetoone synchronization with the business system data, even if the synchronized data is abnormal or nonstandard. Only in this way can the business history be truly preserved, and when data anomalies occur and data is traced, the original business data can be found. Personally,



completely retain business historical data. But there is a problem wrong data business systems can be changed at any time. However, synchronization in offline scenarios will not be performed at any time. And I feel that this is too extreme, and the requirements for personnel and procedures are relatively high. Conversion cleaning during synchronization The second kind of requirements are obviously not so strict and are relatively loose. Rowlevel additions, subtractions, and normalization can be performed during this process.