Approaches-Data warehouse fundamentals-part 2

There are two ways of approaches to Data Warehouse.

Top Down approach or Inmon Approach
Bottom Down approach or Drill Up Approach Or kimball approach

INMON APPROACH (TOP DOWN APPROACH OR DRILL DOWN APPROACH)

First build data warehouse and then load data marts
Faster approach
Bill Inmon definition on data warehouse is – “It is a subject oriented, nonvolatile, integrated, time variant collection of data in support of management's decisions”.
Data mart are dependent on DWH

RALPH KINBALL APPROACH (BOTTOM UP APPROACH OR DRILL UP APPROACH)

Ralph Kimball definition on data warehouse is – “Data warehouse is the conglomerate (Composed of heterogeneous materials or elements) of all data marts within the enterprise. Information is always stored in the dimensional model”.

First build Data Mart and then build data warehouse.

Data marts are independent.

Slow Approach

Comments

BIG Data, Hadoop – Chapter 2 - Data Life Cycle

Data Life Cycle The data life cycle is pictorial defined as show below: As we see, in our current system, we capture/ Extract our data, then we store it and later we process for reporting and analytics. But in case of big data, the problem lies in storing and then processing it faster. Hence Hadoop takes this portion, where it stores the data in effective format (Hadoop distributed File System) and also process using its engine (Map Reduce Engine). Since Map Reduce engine or Hadoop engine need data on HDFS format to process, We have favorable tools available in market to do this operation. As an example, Scoop is a tool which converts RDBMS to HDFS. Likewise we have SAP BOD to convert sap system data to HDFS.

SSIS: The Value Was Too Large To Fit In The Output Column

I had a SSIS package where I was calling a stored procedure in OLEDB Source and it was returning a “The Value Was Too Large to Fit in the Output Column” error. Well, My Datatype in OLEDB source was matching with my OLEDB Destination table. However, when I googled, we got solutions like to increase the output of OLEDB Source using Advanced Editor option . I was not at all comfortable with their solution as my source, destination and my intermediate transformation all are having same length and data type and I don’t want to change. Then I found that I was missing SET NOCOUNT ON option was missing in Stored Procedure. Once I added it, my data flow task ran successfully.

How to Copy or Move Multiple Files from One Folder to Another Folder using Talend

Hello all, In this Post, I will explain how to move Multiple Files from One Folder (Say Source) to Other folder (Say Destination). This Post will also helps you to understand How to Declare Variable and Use it. To Declare a variable, We are go to use Contexts option in repository. Lets say we have two .txt files in Path D:/Source/ . My Requirement is to move the files from Source Folder ( D:/Source/ ) to Destination Folder ( D:/Dest/ ). Step 1: Open a New job Step 2: Now right click and Create a New Contexts from Repository. Give some Name and give Next. Step 3: Now Fill in the Source Directory Details where the loop on files should happen as shown in the snippet and give finish. Step 4: Now Context is created and The values will be changing based on each file in Folder. Step 5: Click and Drag the context from Repository to Context Job Window below the Job Designer. Step 6: If we Expand the Contexts, We can find the variable SourcePath is holdi...

MSBI

Search This Blog