Classic approach |
GeoDAT Data Warehouse - Builder |
|---|---|
Requirements analysis |
Requirements analysis |
Documentation of required databases and tables |
Not required, Required information is collected automatically |
Documentation of required databases, tables and fields
in Words, Access or Excel |
Automatically by definition |
Documentation of extraction rules |
Automatically by definition |
Programming of extraction rules |
Not required. Following the extracion rules definitions the extraction process in GeoDAT- ETL is created without programming |
Create and document Database design for extracted data and for lated delta in staging area |
Automatically, based on previous definitions |
Create extraction tables in staging area |
Automatically, based on previous definitions |
Classic approach |
GeoDAT Data Warehouse - Builder |
|---|---|
| Documentation of transformation rules In Word, Access or Excel | Not required |
| Definition and documentation of replacement tables | Automatically by definition |
| Design of replacement tables | Automatically by definition, automatic table generation included |
| Programmin maintenance programs for replacement tables | Not required |
| Definition and documentation of tables for transformed data | Automatically by transformation rules definition |
| Database table design for transformed data | Automatically by definition, automatic table generation included |
| Documentation and integrate to staging area database design | Automatic assignement of new fields based on transformation rules |
| Creation of tables for transformed data in staging area | Automatically, based on previous definitions |
Not available! |
Based on design patterns all transformation rules are implemented. Results are shown interactively from real data sources |
| Onerous programming of transformation rules | Not required. Following the extracion rules definitions the extraction process in GeoDAT- ETL is created without programming |
Assembling transformed Data into Feld groups
Classic approach |
GeoDAT Data Warehouse - Builder |
|---|---|
| Not available!To our knowledge no procedure offers this possibility | Grouping of tranformed fields into field groups for easy dimension and fact tables design |
Classic approach |
GeoDAT Data Warehouse - Builder |
|---|---|
| Association of single tranformed fields to dimensions and documentation of this mapping | Automatic Mapping by association of fields in field groups to dimensions. |
| Create and document dimension design for hierarchical dimensions ensuring referential integrity | Automatic creation of hierarchical dimensions by precedence of dimensions granting automated referential integrity |
Create and document fact design for by associating dimensions to facts, ensuring referential integrity |
Automatic creation of fact tables by association of dimensions granting automated referential integrity |
| Association of single tranformed fields as attributes of fact tables and documentation of this mapping | Automatic Mapping by association of fields in field groups to fact tables |
Classic approach |
GeoDAT Data Warehouse - Builder |
|---|---|
Source data extraction can only be checked after programming the ETL extraction routines. Database knowledge required. |
No programming required. Immediately after definition of desired extraction behaviour GeoDAT - ETL can
run an extraction and compare results with
the source without any database knowledge. |
| Delta, differnce of last extraction run to the present run. Needs own programming. Database knowledge required for testing. | No programming required. After initial load subsequent runs automatically create delta. Results can be compared to the source without any database knowledge. |
| Transformation needs extensive programming and Testing before running under real conditions. Checking the results requires database knowledge. | No programming required. Transformation run can be started at any time and the results can be compared to the source without any database knowledge. |
| Loading dimensions may be a critical onerous Process which needs dedicated programming checking the results requires database knowledge. | No programming required.
Loading of dimensions can be done ar any time and the results can be compared to the source without any database knowledge. |
| Loading of fact tables is very complex and needs Programming. Checking the results requires database knowledge. | No programming required. Loading of fact tables can be done ar any time and the results can be compared to the source without any database knowledge. |
Update: 05.09.2007 | Total member of visitors:
