Which Database Write Strategy is more efficient for working with larger volumes of data?¶
It is not the amount of data that determines which write strategy would be more efficient to work with. Rather, it depends more on your requirement and what you want to achieve with your data. For example:
- If you want to work with dimensional data and preserve historical records, then Slowly Changing Dimension write strategy is the best option.
- If you want to determine which records have been updated, inserted, deleted, or skipped when you are writing to an existing file destination, the Source Diff Processor should be used in that case.
- If you want to find out which records should be inserted or updated in a database table, the Database Diff Processor would be the more efficient write option in that case.
- If you want to take write actions based on some specific conditions, then use Data Driven Write Strategy.
Note: In Astera Centerprise 9.0, the functionality of the Slowly Changing Dimension write strategy is fulfilled by the Dimension Loader object in the Data Warehouse section of the toolbox.