Online transaction processing, workloads dominated by large numbers of small reads and writes, as handled by Azure SQL Database Hyperscale for instance.
Also called online transaction processing.
Read more: Microsoft Learn
In the Ultra Transcenders books
AZ-305DP-900DP-600DP-700DP-800
Each book explains OLTP in context, with comparison tables and the common traps.
Terms in this definition
- Azure SQL Database
Platform-as-a-service database offered as a single database or in an elastic pool, sized up to 4 TB or 128 TB on Hyperscale. SQL Agent, CLR and queries across databases aren't available.
- Hyperscale
Azure SQL Database tier built for very big databases (as much as 128 TB), offering quick scale operations and read replicas across which load is balanced.
Related terms
- Analytical data processing
Working with big sets of historical data or business measures, mostly reading rather than writing, typically after loading them into a lake, warehouse or lakehouse and on into a semantic model for reporting. It contrasts with OLTP, or transactional, workloads.
- LOB
Line-of-business: the operational applications a company runs on its business data, mostly backed by OLTP databases.
- Memory-optimized table
An In-Memory OLTP table held entirely in RAM, giving very fast access with no latching. SCHEMA_AND_DATA makes it durable and SCHEMA_ONLY doesn't. Azure SQL Database offers it on Business Critical and Premium only.
- NCCI
Nonclustered columnstore index. Placed on an ordinary rowstore table, this updatable index allows analytics to run in real time over live OLTP data. Each table is allowed just one, and a filter can be applied to it.
- Transactional system
Records business events such as payments or orders, one transaction per event. Such systems typically run OLTP workloads against a strongly normalised database.