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 referenced by the new fact table. In this case we need to profile the existing dimensions so that LeapFrogBI knows how to access them. The same is true when using […]
Monthly Archives: May 2012
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 and dimension components. RecordDateTime Definition RecordDateTime is the point in time which the record is considered effective. For example; a transaction is often considered effective at this point in time […]
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 […]
Even LeapFrogBI needs to take a break every once in a while… During maintenance window periods user will be redirected to this page.
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 record with the same composite foreign key. Often this can be resolved by performing an aggregate on the source component. However, it is recommended that this aggregation be performed outside […]
Currently packages output the following detail to the ‘Output’ pane: Information: 0x4004300B at Load via OLE DB, SSIS.Pipeline: “OLE DB Destination” wrote 106886 rows. It would be nice to see the table name that is being written to in this log. Not sure if this comes from the name of the package or the subtask, […]