Skip to main content

Requirements For Data Warehouses


There are some requirements that companies need to meet if they wish to use data warehouses effectively. When first introduced data warehouses in the 1990s, and developed many companies to focus on identifying the data warehouse in the system, which was distinct from the standard operating system.
This view was shared by many of the companies, and also seen in the data warehouse from being a centralized data that are operational. However, over the past decade, many of the companies were to change their views on how they perceive data warehouses. In the 1990s was a decade of trial and error. While there are many successes, there have been many failures.

One of the things that will improve the data warehouse industry is to increase the processing power of the computer. The technology also has advanced to the point where OLAP engines can focus on pulling data rather than placed in a data warehouse. It should also be noted that the field of dimensional modeling has greatly improved over the past decade. To achieve success in the current market, companies need to understand the requirements that must meet if they want their data warehouses to be successful. The companies first thing you want to do is to move from a centralized development strategy to one that is decentralized. In addition, it should also be growing development.

The only thing that companies must be aware that it is inevitable that smaller departments will create their own small repositories. Because he can not stop this practice, it is important for companies to create a framework that allows these departments to share information with the rest of the company. Remember, the purpose of the data warehouse is to give a view of the company as a whole. In spite of all the departments will need their own small repositories to answer crucial questions, you must provide this information to the rest of the company. In spite of this, you should be able to design data-Mart department their own unique way.

The second requirement is that companies will want to meet is the ability to deal with emergencies when they occur variables. The only thing that remains constant is change, and the company must prepare for this. It should be based on a data warehouse in a way that allows them to evolve. It will be frustrating and boring to have to change plans every time the company needs to adapt to the new change. The company must be able to add additional information to their own data warehouse without having to modify any of its components. Once this is done, the company can add new information to their system without having to make changes to boring, and they can focus on more important issues.

The third condition is that companies will want to meet is the rapid implementation. This follows closely to build a system that is decentralized rather than centralized. In the past, companies took months and sometimes years to build a data warehouse, which was central. This is a significant increase in the costs involved with the construction of the system, and the company wasted a great deal of time. Using rapid deployment, the data warehouse can be built in pieces, and it can be done much faster with a high level of efficiency. To do so quickly, it should be to all parts of the data warehouse using the same structure.
Once this is done, it will be much easier for the company to build parts and indexed. And inquire about parts also become much easier. The fourth condition that companies will need to have is the ability to easily dig into simpler form of atomic data.

The vast majority of the company's data clusters need to use atomic data, it is important for departments to access this information without having to give their employees a great deal of training. Another requirement that the company must have is the data clusters that when combined can create the entire data warehouse. It must be shaped pools data from the underlying data (IAEA), because it is not effective to replicate data in all measurements throughout the company.

It is also important for companies to make sure they are repositories of data available 24 hours a day. In the past, the data warehouse will be down for certain periods of time, and this has led to a decrease in efficiency. The existence of data warehouses online 24 hours a day allowing the company to be highly efficient.

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