the OLAP world, there are mainly two different types: Multidimensional OLAP (MOLAP) and Relational

OLAP (ROLAP). Hybrid OLAP (HOLAP) refers to technologies that combine MOLAP and ROLAP.

MOLAP

This is the more traditional way of OLAP analysis. In MOLAP, data is stored in a multidimensional cube.
The storage is not in the relational database, but in proprietary formats.

Advantages:

 Excellent performance: MOLAP cubes are built for fast data retrieval, and is optimal for slicing
and dicing operations.
 Can perform complex calculations: All calculations have been pre-generated when the cube is
created. Hence, complex calculations are not only doable, but they return quickly.

Disadvantages:

 Limited in the amount of data it can handle: Because all calculations are performed when the
cube is built, it is not possible to include a large amount of data in the cube itself. This is not to
say that the data in the cube cannot be derived from a large amount of data. Indeed, this is
possible. But in this case, only summary-level information will be included in the cube itself.
 Requires additional investment: Cube technology are often proprietary and do not already exist in
the organization. Therefore, to adopt MOLAP technology, chances are additional investments in
human and capital resources are needed.

ROLAP

This methodology relies on manipulating the data stored in the relational database to give the appearance
of traditional OLAP's slicing and dicing functionality. In essence, each action of slicing and dicing is
equivalent to adding a "WHERE" clause in the SQL statement.

Advantages:

 Can handle large amounts of data: The data size limitation of ROLAP technology is the limitation
on data size of the underlying relational database. In other words, ROLAP itself places no
limitation on data amount.
 Can leverage functionalities inherent in the relational database: Often, relational database already
comes with a host of functionalities. ROLAP technologies, since they sit on top of the relational
database, can therefore leverage these functionalities.

Disadvantages:

 Performance can be slow: Because each ROLAP report is essentially a SQL query (or multiple
SQL queries) in the relational database, the query time can be long if the underlying data size is
large.
 Limited by SQL functionalities: Because ROLAP technology mainly relies on generating SQL
statements to query the relational database, and SQL statements do not fit all needs (for
example, it is difficult to perform complex calculations using SQL), ROLAP technologies are
therefore traditionally limited by what SQL can do. ROLAP vendors have mitigated this risk by
building into the tool out-of-the-box complex functions as well as the ability to allow users to
define their own functions.

HOLAP
HOLAP technologies attempt to combine the advantages of MOLAP and ROLAP. For summary-type
information, HOLAP leverages cube technology for faster performance. When detail information is
needed, HOLAP can "drill through" from the cube into the underlying relational data.

Types of OLAP Systems

OLAP systems vary quite a lot, and they have generally been distinguished by a
letter tagged onto the front of the word OLAP. ROLAP and MOLAP are the big
players, and the other distinctions represent little more than the marketing programs
on the part of the vendors to distinguish themselves, for example, SOLAP and
DOLAP. Here, we aim to give you a hint as to what these distinctions mean

Relational OLAP (ROLAP) –Star Schema based

Considered the fastest growing OLAP technology style, ROLAP or “Relational”
OLAP systems work primarily from the data that resides in a relational database,
where the base data and dimension tables are stored as relational tables. This
model permits multidimensional analysis of data as this enables users to perform a
function equivalent to that of the traditional OLAP slicing and dicing feature. This is
achieved thorough use of any SQL reporting tool to extract or ‘query’ data directly
from the data warehouse. Wherein specifying a ‘Where clause’ equals performing a
certain slice and dice action.
One advantage of ROLAP over the other styles of OLAP analytic tools is that it is
deemed to be more scalable in handling huge amounts of data. ROLAP sits on top
of relational databases therefore enabling it to leverage several functionalities that a
relational database is capable of. Another gain of a ROLAP tool is that it is efficient
in managing both numeric and textual data. It also permits users to “drill down” to
the leaf details or the lowest level of a hierarchy structure.
However, ROLAP applications display a slower performance as compared to other
style of OLAP tools since, oftentimes, calculations are performed inside the server.
Another demerit of a ROLAP tool is that as it is dependent on use of SQL for data
manipulation, it may not be ideal for performance of some calculations that are not
easily translatable into an SQL query.

Multidimensional OLAP (MOLAP) –Cube based

Multidimensional OLAP, with a popular acronym of MOLAP, is widely regarded as
the classic form of OLAP. One of the major distinctions of MOLAP against a ROLAP
tool is that data are pre-summarized and are stored in an optimized format in a
multidimensional cube, instead of in a relational database. In this type of model, data
are structured into proprietary formats in accordance with a client’s reporting
requirements with the calculations pre-generated on the cubes.
This is probably by far, the best OLAP tool to use in making analysis reports since
this enables users to easily reorganize or rotate the cube structure to view different
aspects of data. This is done by way of slicing and dicing. MOLAP analytic tool are
also capable of performing complex calculations. Since calculations are predefined
upon cube creation, this results in the faster return of computed data. MOLAP
systems also provide users the ability to quickly write back data into a data set.
Moreover, in comparison to ROLAP, MOLAP is considerably less heavy on
hardware due to compression techniques. In a nutshell, MOLAP is more optimized
for fast query performance and retrieval of summarized information.
There are certain limitations to implementation of a MOLAP system, one primary
weakness of which is that MOLAP tool is less scalable than a ROLAP tool as the
former is capable of handling only a limited amount of data. The MOLAP approach
also introduces data redundancy. There are also certain MOLAP products that
encounter difficulty in updating models with dimensions with very high cardinality.

Hybrid OLAP (HOLAP)

HOLAP is the product of the attempt to incorporate the best features of MOLAP and
ROLAP into a single architecture. This tool tried to bridge the technology gap of both
products by enabling access or use to both multidimensional database (MDDB) and
Relational Database Management System (RDBMS) data stores. HOLAP systems
stores larger quantities of detailed data in the relational tables while the
aggregations are stored in the pre-calculated cubes. HOLAP also has the capacity
to “drill through” from the cube down to the relational tables for delineated data.
Some of the advantages of this system are better scalability, quick data processing
and flexibility in accessing of data sources.

Other Types:
There are also less popular types of OLAP styles upon which one could stumble
upon every so often. We have listed some of the less famous types existing in the
OLAP industry.

Web OLAP (WOLAP)

Simply put, a Web OLAP which is likewise referred to as Web-enabled OLAP,
pertains to OLAP application which is accessible via the web browser. Unlike
traditional client/server OLAP applications, WOLAP is considered to have a three-
tiered architecture which consists of three components: a client, a middleware and a
database server.
Probably some of the most appealing features of this style of OLAP are the
considerably lower investment involved, enhanced accessibility as a user only needs
an internet connection and a web browser to connect to the data and ease in
installation, configuration and deployment process.
But despite all of its unique features, it could still not compare to a conventional
client/server machine. Currently, it is inferior in comparison to OLAP applications
which involve deployment in client machines in terms of functionality, visual appeal
and performance.

Desktop OLAP (DOLAP)

Desktop OLAP, or “DOLAP” is based on the idea that a user can download a section
of the data from the database or source, and work with that dataset locally, or on
their desktop. DOLAP is easier to deploy and has a cheaper cost but comes with a
very limited functionality in comparison with other OLAP applications.

Mobile OLAP (MOLAP)

Mobile OLAP is merely refers to OLAP functionalities on a wireless or mobile device.
This enables users to access and work on OLAP data and applications remotely
thorough the use of their mobile devices.

Spatial OLAP (SOLAP)

With the aim of integrating the capabilities of both Geographic Information Systems
(GIS) and OLAP into a single user interface, “SOLAP” or Spatial OLAP emerged.
SOLAP is created to facilitate management of both spatial and non-spatial data, as
data could come not only in an alphanumeric form, but also in images and vectors.
This technology provides easy and quick exploration of data that resides on a spatial
database.

Other different blends of an OLAP product like the less popular ‘DOLAP’ and
‘ROLAP’ which stands for Database OLAP and Remote OLAP, ‘LOLAP’ for Local
OLAP and ‘RTOLAP’ for Real-Time OLAP are existing but have barely made a noise
on the OLAP industry.
ROLAP
ROLAP stands for Relational Online Analytical Process that
provides multidimensional analysis of data, stored in a
Relational database(RDBMS).
MOLAP
------
MOLAP(Multidimensional OLAP), provides the analysis of data
stored in a multi-dimensional data cube.
HOLAP
------
HOLAP(Hybrid OLAP) a combination of both ROLAP and MOLAP can
provide multidimensional analysis simultaneously of data
stored in a multidimensional database and in a relational
database(RDBMS).
DOLAP
-----
DOLAP(Desktop OLAP or Database OLAP)provide multidimensional
analysis locally in the client machine on the data collected
from relational or multidimensional database servers

Sunday, January 18, 2009

Advantages and Disadvantages of ROLAP
Advantages:

-Can handle large amounts of data: The data size limitation of ROLAP technology is the
limitation on data size of the underlying relational database. In other words, ROLAP itself places
no limitation on data amount.

-Can leverage functionalities inherent in the relational database: Often, relational database
already comes with a host of functionalities. ROLAP technologies, since they sit on top of the
relational database, can therefore leverage these functionalities.

Disadvantages:

-Performance can be slow: Because each ROLAP report is essentially a SQL query (or multiple
SQL queries) in the relational database, the query time can be long if the underlying data size is
large.

-Limited by SQL functionalities: Because ROLAP technology mainly relies on generating SQL
statements to query the relational database, and SQL statements do not fit all needs (for
example, it is difficult to perform complex calculations using SQL), ROLAP technologies are
therefore traditionally limited by what SQL can do. ROLAP vendors have mitigated this risk by
building into the tool out-of-the-box complex functions as well as the ability to allow users to
define their own functions.

Sunday, January 18, 2009

Advantages and Disadvantages of MOLAP
Advantages:

-Excellent performance: MOLAP cubes are built for fast data retrieval, and is optimal for slicing
and dicing operations.

-Can perform complex calculations: All calculations have been pre-generated when the cube is
created. Hence, complex calculations are not only doable, but they return quickly.

Disadvantages:

-Limited in the amount of data it can handle: Because all calculations are performed when the
cube is built, it is not possible to include a large amount of data in the cube itself. This is not to
say that the data in the cube cannot be derived from a large amount of data. Indeed, this is
possible. But in this case, only summary-level information will be included in the cube itself.

-Requires additional investment: Cube technology are often proprietary and do not already exist
in the organization. Therefore, to adopt MOLAP technology, chances are additional investments
in human and capital resources are needed.

DATA WAREHOUSE MANAGER

Numerous roles and responsibilities will need to be acceded to in order to make data warehouse efforts successful
and generate return on investment. For the technical personnel (application programmer, system administrator,
database administrator, data administrator), it is recommended that the following roles be performed full-time by
dedicated personnel as much as possible and that each responsible person receive specific Data Warehouse training.
The data warehouse team needs to lead the organization into assuming their roles and thereby bringing about a
partnership with the business. Management also needs to make actionable plans out of these directives and make
sure the staff executes on them.
The following are team and extended team member composition and roles and responsibilities suggestions.
Manager/Director
The responsibilities of the Manager or Director of the Data Warehouse team should be to:
Ensure support for the data warehouse program at the highest levels of the organization
Understand high level requirements of the business
Present the business with the possibilities available to them through data warehousing
Staff the team
Establish and ensure adherence to a set of guiding principles for data warehousing
Communication of key milestone status to IT management
Ensuring the remainder of the team accede to their responsibilities as enumerated below
Liaise with strategic vendors
Establishing partnerships with key IT partners in support of data warehousing initiatives
Project Manager
The perceived strength of data warehousing within an organization will be the sum of the strength of the Project
Managers. Project Managers must deliver commitments and must deliver on time. They will do this by culling
resources from within the data warehouse team and from consultancy as necessary and establishing partnerships
with other internal support organizations required to support a data warehouse iteration. A Project Manager delivers
by:
Maintaining a highly detailed plan and obsessively caring about the progress on it.
Applying personal skill and judgment to everything on the project. This is a real value-add of the Project Manager.
It is the Project Manager’s job to exercise relevant discretion.
Matching team member’s skills and aspirations as closely as possible to tasks on the plan.
Tracking all relevant metrics for each iteration:
o Project Plan milestones
o Issues list
o Adherence to change control practices
o Adherence to source code control practices
o Documentation fit for users and support personnel
o Architectural components adherence to fit for purpose and standards
o Regression testing performed and tests updated based on changes
o Team members fit for tasks and career-enhanced

Chief Architect
The Manager/Director will need to rely on a Chief Architect (or similar title) position, as one of his/her direct
reports, to work on complex issues of architecture, modeling, and tools. The person should be able to quickly qualify
as an authority in data warehousing within the organization and have mastery of the data warehousing paradigm,
both current and emerging technologies. His/her knowledge of the business needs to be just as great. A business
technologist, s/he will meet business objectives with existing or emerging technologies and work on issues with
broad technical or strategic implications. This person would have significant interface with the internal clients and
increase their confidence in the data warehouse organization.
Technical Leader (Data Warehouse Manager)
In case that Project manager role is defined as generic (means that project manager is not forced to know

technical details about the project on deep levels) there is a need for role (person) who would be able to

understand deep business technical details of the project

 Responsibilities

 Managing business domain  and technical aspects of project scope

 Directing people and managing operational issues

 Providing appropriate technical, working and team environment for his team

 Actively helps to PM for projects plans

 Project deliverables and documentation

Required skills

 Must have deep understanding of technical aspect of the project scope.

 Must have significant understanding of business domain which is subject of the project scope .

 Appropriate experience – level is depending to particular project complexity