Transactional (OLTP) vs.

Analytical (OLAP) IT Systems

OLTP: numerous short transactions. Requires fast query processing and
high data integrity in multi-access environments. Effectiveness is
measured by number of transactions per second.
OLAP: low volume of transactions. Complex queries involving aggregation.
Effectiveness is measured by response time. Aggregated, historical data,
stored in multi-dimensional schemas (usually star schema).

Transactional (OLTP) vs. Analytical (OLAP)

IT Systems

The Future of IT Systems:

Combining OLAP and OLTP
Companies no longer have to choose between OLAP and OLTP
platforms like SAP HANA excel in both transactional and analytical
workloads.
Before SAP HANA, no platform could use OLTP and OLAP simultaneously.
Running analytics (operational reporting, data warehousing, Big Data
analysis) the traditional way requires OLTP data to be extracted from the
ERP system and transformed into OLAP data (requires tuning
configurations: aggregates & indexes). Process is slow and cumbersome,
and the quality can be unreliable.
Benefits of combining the two databases: eliminates the necessity of
using a transactional-enabled database management system to do an
analytical workload -> all the data a business needs are in one places
-> saves time, cost, and effort, and improves quality.
Compatible with cloud computing, no hardware lock-in, ensures data
availability and security.