Skip to main content

Rules of Datawarehouse

Once the company has successfully carried out their own data warehouse, it is important for them to establish rules and regulations to be used. While different companies will have different rules when it comes to dealing with their own data warehouses, they are some general principles that you will need to pay attention to.

These principles not only make using your own data warehouse easier, but also allow the organization to be used much more efficiently. Very first rule of thumb is to realize that data warehouses are a challenge to use. And many experts say that at least 30% of the information you give may not be consistent.

One of the most problematic things about this is that the company may not notice the error if they are dealing with an operational unit to be based on the transaction. In spite of this, we should not allow this error rate in the data warehouse. When you consider the fact that many of the stores data on a large-scale can cost millions of dollars to purchase and implement, and 30% error rate is unacceptable. To resolve this issue, it is important for companies to analyze their data carefully before making decisions that are based on it. It is unwise to simply accept the data as it is, without looking carefully for errors or other problems.

The second rule of data warehouses is to understand the data that is stored. It has been said that knowledge is power, but this is only half the truth. Knowledge that is stored and unused is power potential. The companies want to make every day analysis of the databases that are connected to the data warehouse. To understand the data, you should be able to find the relationships between systems analysts are numerous. Once found on these relationships, and must be preserved when transferring data within the data warehouse. The implementation of a data warehouse requires often the user to make some modifications to the schema of the database.

If the user does not understand the relationships between the different systems, they may be prone to generate errors that can adversely affect the accuracy and efficiency of the system. Another important rule of thumb is to learn how to find the entities that are equal to or equal to each other. One of the most common problems that can occur in the data warehouse is when they show the same piece of data in different parts of the machine with different names. For example, two of the departments within the organization may be helping one client, but the name of the Ministry shall not be placed in the system twice under different names.
One name can be provided, and can be another name abbreviation. This can create serious problems in the system if it is not corrected, the best way to solve this problem is to use a data conversion tool. Because many consist of large companies and institutions from many different departments, and can be serious problems arise when each of them decides to store the information in a different way. One of the cases in which this occurs often through mergers. To avoid this problem, companies want to create a standard database structure. This will make it much easier integration when they occur.

Perhaps one of the most important principles of data storage is the use of meta data in a manner supportive of the quality of data within the data warehouse. The metadata can be defined as "data about data." It is data that describes the data within the data warehouse.

One of the biggest challenges facing companies will try to reconcile the metadata across multi-vendor tools. To deal with this problem, the companies want to make sure they generate and use metadata interfaces or other products. Look for vendors who are able to integrate metadata from a variety of sources that are mixed.

It is also important for companies to make sure they choose the right products and data conversion. Data Conversion product is a device that extracts, cleans, and load the data into the data warehouse. It will also record the date of this process. Product data transfer is very important, and companies must carefully choose the product.

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