Skip to main content

Methods of DataWarehouse


Most organizations agree that data warehouses are a useful tool. They benefit from the ability to store and analyze the data, and this can allow them to make sound business decisions. It is also important for them to ensure proper dissemination of information, and it should be easy to access by people who are responsible for making decisions.

There are two elements that make up a data warehouse environment, and this is a supply and staging. It can also be known as a staging area acquisitions. It consists of ETL processes, and once the data has been prepared, it will be sent to the display area.

When data is placed within the display area, a number of programs analysis and consideration. While many organizations agree on the overall goal of data warehouses, may approach to build these institutions vary. Try to use data clusters alone is not a good approach, because they are oriented departments. In addition, we will try to use data clusters alone are ineffective, and it will reach to a number of problems in the long term. There are two techniques for building data warehouses that have become very popular. This is the Kimball Bus Architecture and corporate information factory.

With technology Kimball, will convert the raw data and refined within the staging area. It is important to make sure properly handled data during this step. During the staging process, and will be withdrawn raw data from the source systems. While some of the staging operations may be centralized, and will be distributed to others. The display area has a dimensional structure, and this model will have the same information as a standard model. However, it will be easier to use, and it will display information that is summarized.

Will create a three-dimensional model through business process. Departments within the organization does not play a role in this. Data will be populated once it is placed inside a warehouse dimensions, not depending on the various departments that may make up the organization. When placed inside the warehouse business processes, the system will become highly efficient. Data warehouse approach popular following that you will want to become familiar with is the corporate information factory. Another name for this technique is the approach EDW. Will be the format of the data that is extracted from the source.

In the CIF, the data warehouse is used to hold the record data warehouses, and it may also have specific data warehouses that are designed to extract the data. May be designed for the populations of specific data circuits, and it may be the summary data which is in the form of dimensional structure. The data can be obtained from the data warehouse atomic standard. While there are some similarities between these techniques, there are some notable differences as well.

One of the fundamental differences between these two technologies is the basis of data normalization. With the approach of Kimball, the data structures that must be obtained before displaying depends on the dimensions of the source data and transformation. In most cases, it was not required to store a duplicate of the data in each of the foundations and normalized dimensions. It is believed many of the people who choose to use a normalized data structure that is faster than the dimensional structure, but they often fail to take the ETL into account.

Another thing that separates the two approaches is the management of data warehouse data (IAEA). With CIF, the data will be stored within the data warehouse Atomic normalization. In contrast, the method Kimball States that the atomic data should be placed in the context of the structure dimensions. When data is placed within the structure dimensions, it can be summed up in a wide variety of different ways.
It is important to make sure of the details of the information that you have so that users will be able to ask relevant questions. While most users do not put the focus on the details of the transaction and one offspring, they may want a summary of a large number of transactions. It is important for them to have the details so that they will not be able to answer important questions. Should be the approach you choose to be one which achieves your company's needs.

Comments

Popular posts from this blog

Contact Me

Do You have any queries ?                   If you are having any query or wishing to get any type of help related Datawarehouse, OBIEE, OBIA, OAC then please e-email on below. I will reply to your email within 24 hrs. If I didn’t reply to you within 24 Hrs., Please be patience, I must be busy in some work. kashif7222@gmail.com

Top 130 SQL Interview Questions And Answers

1. Display the dept information from department table.   Select   *   from   dept; 2. Display the details of all employees   Select * from emp; 3. Display the name and job for all employees    Select ename ,job from emp; 4. Display name and salary for all employees.   Select ename   , sal   from emp;   5. Display employee number and total salary   for each employee. Select empno, sal+comm from emp; 6. Display employee name and annual salary for all employees.   Select empno,empname,12*sal+nvl(comm,0) annualsal from emp; 7. Display the names of all employees who are working in department number 10   Select ename from emp where deptno=10; 8. Display the names of all employees working as   clerks and drawing a salary more than 3000   Select ename from emp where job=’clerk’and sal>3000; 9. Display employee number and names for employees who earn commission   Select empno,ename from emp where comm is not null and comm>0. 10

Informatica sample project

Informatica sample project - 1 CareFirst – Blue Cross Blue Shield, Maryland (April 2009 – Current) Senior ETL Developer/Lead Model Office DWH Implementation (April 2009 – Current) CareFirst Blue Cross Blue Shield is one of the leading health care insurance provided in Atlantic region of United States covering Maryland, Delaware and Washington DC. Model Office project was built to create data warehouse for multiple subject areas including Members, Claims, and Revenue etc. The project was to provide data into EDM and to third party vendor (Verisk) to develop cubes based on data provided into EDM. I was responsible for analyzing source systems data, designing and developing ETL mappings. I was also responsible for coordinating testing with analysts and users. Responsibilities: ·          Interacted with Data Modelers and Business Analysts to understand the requirements and the impact of the ETL on the business. ·          Understood the requirement and develope