Modify Lineage Quickly Using “Redirect Source”
Part of the beauty of using LeapFrogBI to define your data mart is how easy it is to make modifications. One example of this is
Deploying Component Modifications
LeapFrogBI provides a toolset that not only streamlines initial data mart deployment, but also greatly simplifies incremental modification tasks. There are a few points that
Dimension Load Using the MERGE Statement
The T-SQL MERGE statement was introduced in SQL Server 2008, and in many ways simplified common tasks such as dimension loading. However, like most things
Schema? Prefix? Both or None?
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
Loading Dimensions From Multiple Sources
Dimensions records are often derived from multiple sources. When these sources are in sync, it is a simple enough process to combine the sources to
Existing Template Source SQL
LeapFrogBI enables the use of existing tables and views. For example; when extending an data mart there will be existing dimensions that need to be
Record DateTime Explained
When creating a PSA component, the designer is asked to assign a value to RecordDateTime. The selected value will have implications downstream on both fact
Handling Failed FK Lookup
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
Aggregate to Prevent Duplicates on Fact Load
When using a merge statement to load a fact table it is important to ensure that the source component/s do not contain more than one
Getting Started 4 of 4: Deploy & Load
New to the LeapFrogBI Platform? You are in the right place. This short video series will help you get started quickly.