LeapFrogBI projects include the option to enable automated notifications per lifecycle based on load process events; start, complete, and failure. To setup the solution simply navigate to the precedence page in the deploy menu, expand the Notification section, and fill out the configuration options. The precedence solution’s poll job controls the notification process by executing bi_notify.dtsx.
Loading a data warehouse requires that a mechanism be created for tracking which source system records have been processed and which are pending. ETL & ELT are very custom processes, but general design patterns are often repeated. In an ideal situation the data integration process will possess these traits: Collection of source system records can […]
Building a data mart can be broken down into three distinct steps. Extact data from source system Transform data to desired structure Load data into target system (data mart) There are many tools available to perform these tasks, but generally speaking we have two categories of tools; database engines and data integration tools (SSIS). Garrett […]
When building a dimensional model it is critical that facts have accurate foreign keys pointing back to related dimensions. However, there are some situations where the fact record is known before the related dimension record. This situation is called a late arriving dimension. Example; We load a sales amount (fact) for a product (dimension) that […]
The Multi-File Stage s9600 template provides a simple method to stage many files with the same structure. The following steps describe how to setup this component. 1. Click “create new” from the stage component page. Find s9600 and download the “File”. This file is an xls file which contains the configuration details for the Multi File Stage tasks. […]
When building SQL Server data warehouses should user-defined schemas be used? Should tables and views be prefixed? Or, maybe we should do both. After talking to a few people about this and doing a little research, one thing is clear. Deciding to use schemas and/or prefixes is much more of a personal preference than it […]
When a fact component attempts to load a record, a foreign key to a dimension lookup is performed. This lookup (join) may fail if the dimension does not have a record that meets the fk join definition. In this case LeapFrogBI will place a -1 in the FK_#### field to flag it as an unknown dimensoin […]