liveBook · Manning

Database page

A database page is a fixed-size unit of physical storage containing rows or portions of rows from database objects.

How 2 Manning books explain it

Just Use Postgres!

A database page is a fixed-size unit of physical storage that holds multiple database table or index records.

How it is used
Explains how physical row placement creates locality that supports BRIN indexing for large time-series tables.
How deep it goes
Defines page size and filling behavior, then connects page locality to BRIN indexes without detailing page internals.
Examples
Uses appended heart-rate measurements, page-by-page timestamp ranges, BRIN creation, index-size output, and query execution plans.
What you can do after
Evaluate how append order and page locality can influence BRIN index suitability and query execution.

Read how Just Use Postgres! explains database page →

100 SQL Server Mistakes and How to Avoid Them

A data page is a fixed-size SQL Server storage unit containing rows or portions of rows from database objects.

How it is used
Supports SQL Server table storage, indexing, and buffer-cache-based query execution.
How deep it goes
Explains page placement in heaps and indexes and traces cache loading, but does not detail page-size internals.
Examples
Uses heap and clustered-index diagrams plus a product lookup demonstrating selected columns and NOLOCK.
What you can do after
Evaluate how table organization and query breadth affect page reads, cache pressure, and lookup performance.

Read how 100 SQL Server Mistakes and How to Avoid Them explains database page →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.