Skip to main content

How to build DataWarehouse

And the structure of the data warehouse consists of elements and components that make up the database. Structure will show how the components work together, and can also show how the database will grow over a certain period of time.

While each has a data warehouse structure, and only a few of them a high degree of organization. It is important to note that the data warehouse with the structure of the organization is the most likely to succeed. A data warehouse without the presence of the structure of the organization not be as flexible as it should be. In the absence of good faith, there would be no contacts, they will become difficult to maintain database.
If the company aspires to compete successfully, it is necessary to design the structure of a data warehouse that is highly organized and efficient-A "blue print" to make sure they are properly designed. Must be the definition of all the components, and show how the system will grow as they are used. Thus, it is important to build a data warehouse with the right structure.

The first thing is important to realize that the structure of your data warehouse should be connected directly to your business. For example, if you need to design a data warehouse, which will be updated every night, you will need this to be built in the structure. To build this function in the temple, you will need to have a technical understanding of the system. Some of the things you may want to build a structure within your data warehouse is the availability of global, customer analysis, and data sources, reliability, and daily updates. It is also important to look at the components that will form the structure.

Two core components that will form the structure of your data warehouse is the art elements and data elements. You will also need to consider the business processes, devices, networks, and operating systems. When it comes to data, you may need to create a structure that provides information related to billing or shipping. Should the data within the data warehouse has the same structure. It should also be kept in the same way. A common question that is raised between the organizations is the decision of whether the data appears in dimensional or entity / relationship.

The one you choose depends on how you run your organization. Once you have made your decision, you will want to consider the next infrastructure architecture. The most important factors that are related to infrastructure architecture is the flexibility, size, and scalability. If you do your research, you should not have a hard time building this. When it comes to the network, you will need to pay attention to data sources. There must be a sufficient amount of available bandwidth to transmit information. Must be on desktop computers, which used to be strong enough to run the necessary programs. In addition, should the software you use will be easy to transfer between machines.

It should also put emphasis on the technical architecture. The process must be used which is based off the metadata catalog. It should be a data warehouse is able to pull data from many sources, and may require this data to be encrypted or compressed. You will also need to make sure the data transfer correctly, it should be cleaned, integrated, and audited. It is also important to make sure that you download to many of the goals.

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