Online complex processing (OLCP) is a database workload label rather than a single industry standard. In Teradata’s official documentation, it is used for tactical queries: short, highly tuned queries that support operational decisions. Teradata places these queries close to online transaction processing (OLTP) because both need short response times, but it separates them by purpose and workload mix. Other sources use the term more loosely, so the meaning depends on who is writing.
What OLCP means in Teradata’s usage
Teradata’s documentation gives the category its name in one sentence: “The name tactical query is given to a certain category of work that is short, highly tuned, and focused on more operational decision-making.” (Teradata documentation, Tactical Queries Defined.)
In that usage, the label describes what a query is for and how it is tuned, not how large it is. A short query that feeds a live operational decision falls in the category; a long batch report does not.
How OLCP differs from OLTP
Teradata draws the line on purpose. OLTP mainly records operational events and bookkeeping, usually with a higher share of writes and a narrower departmental context. Tactical OLCP queries support operational decisions, lean more toward reads, and can draw on a broader enterprise context.
#1 Best Overall
| Aspect | Tactical OLCP (Teradata usage) | OLTP (as Teradata describes it) |
|---|---|---|
| Primary purpose | Supporting operational decisions | Recording operational events and bookkeeping |
| Workload mix | More read-intensive | Higher ratio of writes |
| Context | Can use a broader enterprise context | Narrower, often departmental context |
| Response time | Short; a flexible range is given in the next section | Short response times are also needed; no specific range is stated in Teradata’s comparison |
The comparison is about purpose and workload profile. Two systems can both be fast and still fall on different sides of this line.
Response-time expectations
Teradata says tactical query response requirements can range from subsecond to 10 or 20 seconds or more. The figure is an illustration of how wide the tactical category can be. It is not a promised latency or a general OLCP service-level target, and the page does not state a publication date. Your own application requirements should set the number.
Where the term came from
A 1992 database white paper credits InterBase with coining “online complex processing” in the late 1980s. It contrasts OLCP’s variety of complex operations with simpler OLTP environments. This is useful historical context, but it is a single attribution. It does not establish a formal, industry-wide definition.
Why definitions vary
A short dictionary-style entry describes OLCP as real-time processing involving complex or lengthy queries and/or simultaneous reads and writes to the same records. That meaning is broader than Teradata’s tactical-query usage. Because the entry is terse and not a technical specification, it should not override vendor documentation when you are working on a specific platform.
When you encounter OLCP in a document, check the following:
- Author or vendor: Is the term Teradata’s tactical-query usage, the dictionary sense, or a historical 1980s-era usage?
- Scope: Does the source describe query purpose, read/write mix, or both?
- Numbers: Is a response-time figure a vendor example or a requirement that applies to your system?
Tuning note: dictionary cache
Teradata’s performance documentation says OLCP and tactical workloads may benefit from a larger dictionary cache when plans are not already in the request cache. More dictionary details then remain available for parsing and optimization. The same documentation notes that workloads running longer than a minute may see no measurable difference from a larger cache. This is product-specific guidance. The right setting depends on your system and workload, so measure the effect before changing it.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
