Skip to content
BENIBIX Learn

Row-Oriented Storage

Also known as Row Storage, Row Store, Row-Based Storage

Each row is kept together on disk. It is quick for one record at a time.

Think of it like

It is like a stack of cards, one per person. Each card holds all about that one person.

Example

When Jack places an order, the shop's database writes his whole order row in one place. Showing his order later reads that one spot.

Why it matters

It is why app databases handle many small writes fast. It is also why big reports on them are slow.

Definition

Row-oriented storage keeps all the values of one row next to each other on disk. Reading or writing one whole record is quick, because it sits in one place. Reading one column from many rows is slow, because every full row must be read. Most databases that run apps store data this way. Warehouses tend to use columnar storage instead.
Row storage is the left layout. Each row's values sit side by side on disk.

Common mistake

Running big reports on the app's own database. Each report reads every row in full, and the app slows down for its users.

Key takeaways

  1. 1
    Rows together. A record's values sit side by side.
  2. 2
    Fast for one record. Read or write a row in one go.
  3. 3
    Slow for one column. Sums must read every full row.

Compare