
In this lecture, we start with the need of ETL framework and how is it important for any Data Warehouse project.
A quick run thru of what will be covered in this course at a very high level.
Answers to the commonly asked questions by the participants from other courses (Data Warehouse Concepts, Informatica Developer, Informatica Administrator).
In this lecture, we will talk about the architecture we will use for this course.
Let's take a look at the different stage in this lecture.
Business metadata includes definitions of data files and attributes in business terms. It may also contain definitions of business rules that apply to these attributes, data owners and stewards, data quality metrics, and similar information that helps business users to navigate the information of the enterprise.
Technical metadata is the most common form of metadata. This type of metadata is created and used by the tools and applications that create, manage, and use data.
Operational metadata contains information that is available in operational systems and run-time environments. It may contain data file size, date and time of last load, updates, and backups, names of the operational procedures and scripts that have to be used to create, update, restore etc.
This section covers the process flow and different activities which should be taken care during the ETL framework implementation from file validations, Exception handling and Audit Control.
Sourcing or Extracting or Pulling the data from source systems in the form of flat files, XML files, relational databases, message queues, webservice calls, API's, cloud based connectivity, application connections etc. is called Data Sourcing. In this lecture, we understand the Data Sourcing process.
The different methods/events in which the Data Sourcing can be done are the following
The different methods/events in which the Data Sourcing can be done are the following
The different methods/events in which the Data Sourcing can be done are the following
The different methods/events in which the Data Sourcing can be done are the following
The different methods/events in which the Data Sourcing can be done are the following
The architectural classification for the Push/Pull mechanism is discussed in this lecture.
In this lecture, the different logical areas to be covered as part of the code are discussed.
Functionality to be included
Standard file validations
Standard file validations
Failure Validation
In this lecture, we talk about the need of the staging layer and how it will be useful for the Data Warehouse projects for performing the Data Validation and Business Validations.
Should Reference Data be stored in Staging layer. Let's find out.
Different examples of the Reference data are discussed in this lecture.
In this lecture, we will see if the Staging layer should have the Audit attributes included or not.
In this lecture, we talk about the number of days the data should be kept in the Staging layer and how this is related to the Business decision.
In this lecture, we talk about the best practices for creating the partitions included in the Staging layer.
We will quickly review the basic Data base standards to be followed for the Staging layer.
In this lecture, we talk about the Business Validation Layer. All the Business Critical Aggregations and Calculations happen in this layer.
In this lecture, we will talk about the different situations possible for the file loads.
In the Informatica PowerCenter, there are two ways to load a flat file into a Target definition:
Direct and Indirect.
We can set the Source File type to ‘Direct’ when loading a single flat file. ‘Indirect’ Source File type is when you need to load multiple flat files.
In large data integration projects, it is quite common to source data from multiple systems, sources, regions etc. As the number of data sources increases, the ETL load time also increases, because of the increasing data volume. One way to reduce the load time is by running different ETL process in parallel. Informatica PowerCenter's capability to run workflow concurrently can be used in such scenarios to reduce the ETL load time.
Are partitions really required for Staging and Business validation layer? Let's find out in this lecture.
Once the Stage load is complete, Dimension load will be triggered. For each business context, there would be a separate dimension table.
Source File Management or Archival is another important requirement which is usually ignored during the inception of the project or the requirement scope. This is as important as the data processing requirements. In this lecture, we understand how this will be done.
This course provides a high level approach to implement an ETL framework in any typical Data Warehouse environments. The practical approaches can be used for a new application that needs to design and implement ETL solution which is highly reusable with different data loading strategies, error/exception handling, audit balance and control handling, a bit of job scheduling and the restartability features and also to any existing ETL implementations. For existing implementations this framework needs to be embedded into the existing environment, jobs and business requirements and it might also go to a level of redesigning the whole mapping/mapplets and the workflows (ETL jobs) from scratch, which is definitely a good decision considering the benefits for the environment with high re-usability and improved design standards.
This course is a combination of standard and practical approaches of designing and implementing a complete ETL solution which details the guidelines, standards, developer/architect checklist and the benefits of the reusable code. And, this course also teaches you the Best practices and standards to be followed in implementing ETL solution.
Though this course, covers the ETL design principles and solutions based on Informatica 10x, Oracle 11g, these can be incorporated to any of the ETL tools in the market like IBM DataStage, Pentaho, Talend, Ab-intio etc.
Multiple reusable code bundles from the marketplace, checklists and the material required to get started on UNIX for basic commands and Shell Scripting will be provided.