標題: There needs to be a unique key [打印本頁] 作者: JOSNA777 時間: 2024-3-7 12:08 標題: There needs to be a unique key You can also perform operations such as field aggregation, association, conversion, etc. In fact, for product design, if this form is supported, onetoone synchronization is supported. There is this conversion and aggregation capability during the synchronization process. If not used, it will be onetoone synchronization. In this way, onetoone synchronization seems to be more of a norm and a requirement. Target table type for transfer The goal of moving business data to the data platform is to preserve history and make data traceable. However, the data of the business
system changes all the time, so how to retain the history Austria WhatsApp Number of the changed data is a problem of creating the target table structure. This is actually part of the field of data warehouse modeling. Why do I mention it here Let’s first talk about some common forms of target tables. Full table, slice table, zipper table. Full scale The full scale is the same as the name, that is, all data is synchronized to the target. Try it for tables with little data changes, such as synchronization code tables. Slice table The slicing table is divided into incremental slicing and full slicing. Full slicing means placing all
daily business data in the current day's partition. Incremental slicing means only placing the current day's delta in the current day's partition. Zipper list The zipper table is the most complex. and you need to know whether the business data has changed. After the change, add a new entry in the target table to record the start time and end time of the changed data. Some also have fields such as version and current status (zipper table). It also depends on the time granularity of synchronization.
