There are many ways to deal with records that have been deleted from a source system. The first decision is to determine if the deletion needs to be reflected in the target model. Then we need to figure out how we will know when a delete has occurred and identify the deleted records. For an […]
Two new design patterns are now available. These design patterns, DP-4100 & DP-4101, generate all required components and related logic to track source system deletes via a soft delete tracking field in PSA. Standardize on these design patterns and adjust to meet unique needs as required. Get the job done in seconds and stay agile!
What to do when a data warehouse source system deletes a record? There are probably hundreds of answers to this question. If you want to review a few of the options, then check out this post. For the sake of brevity, I am going to focus the situation as follows: The data source hard deletes records […]
Anyone who has been involved with data warehousing knows that there are plenty of things that can go wrong. Mistakes can be made when researching the data sources, collecting requirements, designing a dimensional model, etc… Assuming all of the analyst and modeling work has been done perfectly, we still need to be sure that the […]
This initial load of a dimension can be a resource intensive process. The situation gets even tougher when the dimension’s natural key is not optimal; composite and/or string data types. The new D1003 template is up to the challenge. Give it a try and experience 40% to 90% performance increase!
LeapFrogBI’s dimension templates are designed to handle a number of use cases. Below is a list of currently available templates, along with a short description of their capabilities & characteristics. Cliff’s Notes Version – Use D1003 as your default dimension template. This template is the most advanced in capabilities and performance. D1000 – Single Batch Description: […]