Skip to main content

The Data Warehousing Process

Stage 1 :

Determine Informational Requirements
• Identify and analyze existing informational capabilities.
• Identify from key users the significant business questions and key metrics that the target user.Group regards as their most important requirements for information.
• Decompose these metrics into their component parts with specific definitions.
• Map the component parts to the informational model and systems of record.

Stage 2 :

Evolutionary and Iterative Development Process

When you begin to develop your first data warehouse increment, the architecture is new and fresh. With
the second and subsequent increments, the following is true:
• Start with one subject area (or subset or superset) and one target user group.
• Continue and add subject areas, user groups and informational capabilities to the architecture
based on the organization’s requirements for information, not technology.
• Improvements are made from what was learned from previous increments.
• Improvements are made from what was learned about warehouse operation and support.
• The technical environment may have changed.
• Results are seen very quickly after each iteration.
• The end user requirements are refined after each iteration.
Data Warehousing is an evolutionary/iterative process that follows a spiral pattern
• The warehouse architecture is initially developed at the start.
• The first increment is developed based on the architecture.
• Building the first increment causes architectural changes.
• Operation of the warehouse brings architectural changes.
• Each additional increment extends the warehouse.
• Each new increment may cause architectural adjustments.
• Continued operation may cause architectural adjustments.







Comments

Popular posts from this blog

ODI KM Adding Order by Option

You can add Order by statement to queries by editing KM.I have edited IKM SQL Control Append to provide Order by.  1) Add an option to KM named USE_ORDER_BY, its type is Checkbox and default value is False. This option determines you want an order by statement at your query. 2)Add second option to KM named ORDER_BY, type is Text. You will get order by values to your query by this option. 3) Editing Insert New Rows detail of KM. Adding below three line code after having clause. That's it! <% if (odiRef.getOption("USE_ORDER_ BY").equals("1")) { %> ORDER BY <%=odiRef.getOption("ORDER_BY" )%> <%} %>  If USE_ORDER_BY option is not used, empty value of ORDER_BY option get error. And executions of KM appears as such below; At this execution, I checked the KM to not get errors if ORDER_BY option value is null. There is no prove of ORDER BY I'm glad.  Second execution to get  Ord...

Synchronous and Asynchronous execution in ODI

In data warehouse designing, an important step is to deciding which step is before/after. Newly added packages and required DW data must be analyzed carefully. Synchronous addings can lengthen ETL duration. Interfaces, procedures without generated scenario cannot be executed in parallel. Only scenario executions can be parallel in ODI. Default scenario execution is synch in ODI. If you want to set a scenario to executed in parallel then you will write “-SYNC_MODE=2″ on command tab or select Synchronous / Asynchronous option Asynchronous in General tab. I have created a package as interfaces executes as; INT_JOBS parallel  INT_REGIONS synch  INT_REGIONS synch  INT_COUNTRIES synch  INT_LOCATIONS parallel  INT_EMPLOYEES parallel (Interfaces are independent.) Selecting beginning and ending times and durations from repository tables as ODI 11g operator is not calculating these values. It is obvious in ODI 10g operator. SELECT    sess_no...

Oracle Data Integrator tools: OdiFileDelete and OdiOutFile

Hello everyone! It’s time for another cool ODI tutorial. Last time, I spoke about the   OdiZip tool and how it can be used to create zip files from a directory. Through this post, I will talk about two more tools related to  Files  namely  OdiFileDelete and  OdiOutFile . 1. OdiFileDelete The  OdiFileDelete  is a tool used to delete files present in a directory or a complete directory on the machine running the agent. Usage OdiFileDelete -DIR=<dir> | -FILE=<file> [-RECURSE=<yes|no>] [-CASESENS=<yes|no>] [-NOFILE_ERROR=<yes|no>] [-FROMDATE=<fromdate>] [-TODATE=<todate>] If  -FROMDATE  is omitted, all files with a modification date earlier than the  -TODATE  date will be deleted. If  -TODATE  is omitted, all files with a modification date later than the  -FROMDATE  date will be deleted. If both parameters are omitted, all files matching the  -FILE...