Append FAQS

1. What is the Append integration strategy?
• The Append strategy involves inserting the incoming data flow directly into the target datastore, optionally deleting all existing records in the target table before insertion.
2. Does the Append strategy delete the existing data in the target table?
• Yes, the Append strategy typically deletes (or truncates) all records in the target table before inserting the new data. This step depends on the selected Knowledge Module (KM) option.
3. How is data inserted into the target datastore?
• Data is inserted from source tables into the target datastore using a direct INSERT/SELECT statement. The SELECT clause handles transformations from the staging area, while the INSERT clause handles transformations on the target.
4. What happens if the source data is on a different server?
• If the source data is on a different server, the Loading Knowledge Module (LKM) will have already prepared the loading tables to facilitate data integration.
5. What is a Knowledge Module (KM) option, and how does it affect the Append strategy?
• A KM option is a configuration that controls various aspects of the integration process. In the Append strategy, KM options manage tasks like committing transactions or truncating the target table before data insertion.
6. How is the transaction handled in the Append strategy?
• The operations performed on the target table should be done within a transaction. After all operations are complete, the transaction is committed, typically triggered by a KM option called COMMIT.
7. Can I use Control Append instead of Append?
• Yes, the Append strategy can also be implemented using the Control Append strategy, but if flow control is not activated, both strategies will function similarly.
8. What transformations are applied during the Append strategy?
• All necessary transformations are applied both in the staging area (before loading into the integration table) and on the target (during the INSERT phase). These transformations could include filtering, joins, and other data manipulations.
9. When should I use the Append strategy?
• The Append strategy is useful when you need to load new data into the target datastore and are either not concerned with existing data or are clearing out old records before loading new ones.
10. Is there any impact on data integrity when using the Append strategy?
• The Append strategy can overwrite existing records if the target is cleared before insertion. Therefore, ensure that the strategy aligns with your business requirements and data integrity needs. If you need to preserve historical data, other strategies (like Incremental Update or Slowly Changing Dimension) might be more appropriate.