The Append integration strategy inserts the incoming data flow directly into the target datastore, potentially deleting the existing data beforehand.
Steps Involved in the Append Strategy:
- Delete or Truncate Existing Records:
- The first step is to delete (or truncate) all records from the target table. This step usually depends on a specific Knowledge Module (KM) option.
- Transform and Insert Data:
- Data is loaded from the source tables (either on the same server or from remote sources).
- For data on the same server, it can be read directly into the integration process.
- For remote data, the Loading Knowledge Module (LKM) will have prepared the loading tables.
- The integration operation performs a direct INSERT/SELECT statement:
- SELECT clause: Contains all transformations performed in the staging area.
- INSERT clause: Contains transformations performed on the target.
- Commit the Transaction:
- All operations performed on the target should be within a transaction.
- After completing the operations, the transaction is committed.
- Committing is typically triggered by a KM option called COMMIT.
- Alternative with Control Append:
- The same integration strategy (Append) can be achieved using the Control Append strategy if flow control is not activated. This results in the same data integration process without additional flow management.
No comments:
Post a Comment