Users can now add custom scripts to components. For example, add indexes or update statistics using t-sql scripts. Built components will include the provided custom script. By storing customization along with project metadata deployment, modifications, and ongoing maintenance are further
Monthly Archives: October 2012
LeapFrogBI is a SaaS metadata driven ETL platform. At no time does LeapFrogBI connect directly to either the source or the destination systems. Therefore, the first step in building a data mart is to provide metadata to LeaFrogBI in the
The new f9001 component automates deletion of records from a fact table. Simply select the fact table to effect and a source to inner join to the fact table. Apply any required filters and all matched records will be deleted
There is a wealth of data available via REST API much of which is publicly available. LeapFrogBI simplifies and automates the process of extracting data from these sources.
Step 1: Create REST Stage
Component s9501 will create a package which
There is a wealth of data available via REST APIs much of which is publicly available. LeapFrogBI simplifies and automates the process of extracting data from these sources. Simply fill out a configuration file, build a stage component (s9501), and
I get asked on occasion to quantify the efficiency that LeapFrogBI offers. Below are a few measures that were collected on a recently completed data mart project.
Developers: 2 with some data warehousing experience
LeapFrogBI Experience at Project Start: None