They may have 1-2 new items each day, which makes for significantly smaller tables without the need to incrementally load.įor Discovery Hub to enable this feature, there are two prerequisites needed in the source data of the table. Using our grocery store example, while they may have thousands of updated transaction each day, their list of items on the shelves changes at a much slower pace. While this configuration may be preferable for transaction tables, it may not be necessary or even desired for dimension tables. If Incremental Load is enabled on the transaction tables in each database, it reduces the total number of records that need to be loaded, and therefore drastically reduces the total time it takes to refresh an organization's analytical infrastructure. This considerable amount of data could take hours to load for just this single table. Over time, this table would become very large, storing millions or billions of records. Say for example a grocery store that logs thousands of transactions each day in a Sales table. This configuration is typically preferable on large transaction tables. Incremental Load is the process of loading ONLY the new or modified records during an execution.
0 Comments
Leave a Reply. |