Skip to main content

Datawarehouse Disadvantages


Many of the vendors spend a great deal of time talking about the advantages of data warehouses, and why companies need them if they wish to survive in the global market. While there is a degree of truth in the statements made by many vendors, it is important for companies to realize that data warehouses are not a panacea, and find a solution to all the problems you will encounter the company.

To be able to maximize the efficiency of the data warehouse requires the company to look at it from multiple perspectives, and that includes those that are both positive and negative.

The ultimate goal of the data warehouse system for storing historical information about the transactions of the company, and provide these Ψ₯ΩŠΩ†ΩΩˆΨ±Ω…ΨͺΩŠΩ† in a way that will allow the business to make important decisions. However, these data do not constitute only a small part of the information that it needs to operate, and its value, but may be limited. In some cases, the end user does not have a strong interest in the old data processing, and a lot of this data is provided in the basic reports. Many of the markets that operate in today's companies are in constant transition. Depending on the circumstances, it may not be necessary to use a historical system.

In other words, data warehouses may be too much for most companies. This is especially true for many small businesses and medium-sized businesses that are analyzing their dealings with the need for expensive programs. One of the criticisms that are usually made of data warehouses is complexity. Implementation of a data warehouse can be complex so that they can make business processes more difficult to deal with. Some experts said that even these complications can ultimately stifle business. If the company is able to put less emphasis on some of the processes, the data warehouse can cause in the business environment to become more cluttered than that.

The second problem which has become very common with data stores is its cost. Like all the advanced technology, and when it was displayed for the first time data warehouses, and can only be for wealthy companies really afford it. Even today, most data warehouses are outside the price range of companies that do not fall under the Fortune 500 or 1000 class. While sellers in recent years begun tailoring their products to small businesses and medium-sized enterprises, many of these companies may not see the need for use that are very complicated. Given the speed in the world of business, and many companies are not patient enough to wait for the implementation of the data warehouse.

In the past, it was not uncommon for a data warehouse project to take several months to implement. In one case, it took 18 months to fully implement the system. Most of today's companies want results, and they want them quickly. They do not see the need to wait for months on the system did not prove, and can become inevitably fail. The return on investment for data warehouse projects are usually much lower than the sellers promise, and it will take a long time before the company begins to see a return on their investment. Many companies simply do not have the patience to wait for the returns.

It is also important for companies to pay attention to the data side of the warehouse. Because of the complexity of these systems, it can be said that data warehouses can take on a life of their own. It must be emphasized that the development of the data in the data warehouse for adding not for any specific purpose can reduce its value.

When you combine this with the fact that the costs involved with maintaining a data warehouse can become bigger, it is easy to see why companies should be careful in their decision to use it.


Data warehouses is a technology that has brought a great deal of success for many companies. However, many of the vendors paint a rosy picture, and fail to talk about the challenges facing the company. This is done because of the fact that the seller wants to sell the product. Companies must carefully analyze the organization to decide whether the data warehouse is conducive to their needs. Only after they've done this analysis can decide whether the data warehouse and really worth the time and cost.

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