Teradata was the first to announce a database that could handle 1TB of data. They developed a database that was built to work on a massively parallel scale and hence the high speeds in working with large volumes of data. Teradata was (for at least five years in succession) one of the fastest growing company at that time.
IBM published “Information Warehouse” framework as early as 1987 and hence can be regarded as the other pioneer of data warehousing.
Enterprise Data Warehousing has been the key trend in corporate computing in the 1990s and continues to be so today.
Business Intelligence (BI) is just a fancy term for reporting. If I ask a business user what a report is, he/she will be able to bring up an image in their head of what it is and explain it as well. To make it easier to understand BI, just consider it as a reporting mechanism. That begs to the question why we have a fancy term like BI for a simple concept like reports?
As a consultant I am usually making recommendations to customers for processes and products. On a recent discussion with a client (a major bank) I was basically working out an enterprise architecture to support their reporting requirements. In a move to consolidate its operations and personnel the bank has made a central body to take charge of ALL reporting requirements of the organization locally as well as globally. Continue reading →
As part of the ‘basic’ series, we now come to the world of OLAP and the various concepts, technologies and tools in it. In my previous post on OLTP and OLAP, we saw the difference (conceptually) between what comprises an OLTP system and what would be considered as an OLAP system.
Having understood the fundamental concept of OLAP, lets go down the rabbit hole and see what other wonders we find. To jumpstart the process I’ll throw at you the 3 acronyms you are bound to hear when OLAP pops up and that is MOLAP, ROLAP and HOLAP. They are the three stooges of OLAP.