There needs to be a unique key
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 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 scaleThe full scale is the same as the name that is all data is Austria WhatsApp Number 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
https://lh7-us.googleusercontent.com/4FckHUwXk3b92snLoDsNzrVJcXT1eSqDqWXgeJIB4sT-A1jo3qhBhnNIWbIBnkPMRRlWQ5LQRsfWAYdlUn6VTcUfU72jwfONZg5faKDa3GIYAxGBJPDHtuDWwZ0FYxr_cyqhb24I_k9lRKAzhefNi1Y
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 If the time granularity is finer there may be situations where the data cannot be synchronized to the target Why do I say it here Because data integration products need to functionally support the table creation types of these target tables .
頁:
[1]