Can use the same DB structure for both operational OLTP database and for BI/reporting relational data source
without loosing query performance

Yes (with OLAP)

Yes

No

No

Requires complex ETL for denormalization and pre-aggregation for optimal performance

No (if OLAP)

No

Yes for normalization, no for pre-aggregation

Yes

MOLAP and HOLAP supported

Yes

Yes

No

No

ROLAP supported

Yes

Yes

Yes

Yes

Data refresh latency

Latency equals time for snapshot/replication + cube processing.
Tabular model has cold run latency but no cube processing latency.
OLAP cube processing latency depends on MOLAP / ROLAP / HOLAP design of partitions.
We recommend to use ROLAP for a partition with the latest data.ROLAP means no cube processing latency.

Latency equals time for snapshot/replication + cube processing.
It depends on MOLAP / ROLAP / HOLAP design of partitions.
We recommend to use ROLAP for a partition with the latest data.ROLAP means no cube processing latency.

Latency equals time for ETL + time to build columnstore indexes+ time for slow cold run. Complex ETL with denormalization takes more time.

Latency equals time for ETL.Complex ETL with denormalization takes more time.

Requires built cubes or basic skills to design them using a wizard

Yes for OLAP, No for Tabular

Yes

No

No

Requires troubleshooting skills with cube processing for operational support