SQL Pagination Across Databases: LIMIT, TOP, and OFFSET-FETCH Compared

By Sharon Ben-Moshe · August 2, 2026 · 2 min read

Sharon Ben-Moshe is the founder of sqlfmt, a browser-based SQL formatter and validator with misspelled-keyword suggestions across PostgreSQL, MySQL, SQLite, SQL Server, and BigQuery.

PostgreSQL, MySQL, and SQLite page results with LIMIT. SQL Server uses TOP or OFFSET-FETCH. BigQuery uses standard LIMIT/OFFSET. Here's how the syntax — and the gotchas — differ.

Quick answer

PostgreSQL, MySQL, SQLite, and BigQuery all paginate with LIMIT n OFFSET m. SQL Server instead uses either SELECT TOP(n) or, for true offset-based paging, OFFSET m ROWS FETCH NEXT n ROWS ONLY — and that clause requires an ORDER BY, unlike LIMIT elsewhere.

FAQs

Does SQL Server support LIMIT?

No. SQL Server has no LIMIT keyword — use TOP(n) for a simple row cap, or OFFSET ... FETCH NEXT ... ROWS ONLY for offset-based pagination.

Why does my MySQL LIMIT return the wrong rows?

Check the argument order. MySQL uniquely supports LIMIT offset, count as well as LIMIT count — mixing them up silently returns a different page than intended, with no error.

Does OFFSET/FETCH need ORDER BY in SQL Server?

Yes, it's mandatory — SQL Server raises a syntax error if OFFSET ... FETCH NEXT is used without a preceding ORDER BY.

Is pagination deterministic without ORDER BY?

No, in any of these five dialects. Without an ORDER BY on a unique or near-unique column, the database can return rows in a different order between two otherwise-identical paged requests.

Does BigQuery support OFFSET?

Yes — BigQuery uses the same LIMIT n OFFSET m syntax as PostgreSQL, MySQL, and SQLite.

SQL Dialects

The Comprehensive Guide to SQL Data Types: Storage, Precision, and Cross-Dialect Portability

By Sharon Ben-Moshe · Oct 13, 2026

The complete guide to SQL data types across PostgreSQL, MySQL, SQL Server, and SQLite. Numeric precision, character sets, timestamps, and JSON.

Read post

SQL Dialects

The Definitive Guide to SQL Window Functions: Syntax, Framing, and Real-World Recipes

By Sharon Ben-Moshe · Oct 13, 2026

The comprehensive guide to SQL window functions. Master OVER, PARTITION BY, ORDER BY, window frames (ROWS vs RANGE), and ranking recipes.

Read post

SQL Dialects

Try it now

Paste your SQL into sqlfmt — format, validate, and catch typos free in your browser.

Open SQL Formatter →

PostgreSQL, MySQL, SQLite, and BigQuery: LIMIT and OFFSET

Standard LIMIT/OFFSET pagination

SELECT id, title
FROM posts
ORDER BY published_at DESC
LIMIT 20 OFFSET 40;   -- page 3, 20 rows per page

This works unchanged in PostgreSQL, SQLite, and BigQuery. MySQL supports the same form, plus a reversed comma syntax — offset first, count second — that's easy to get backwards when porting a query from another dialect.

MySQL's alternate comma syntax

-- MySQL only: offset, count — not count, offset
SELECT id, title FROM posts ORDER BY published_at DESC LIMIT 40, 20;

SQL Server: OFFSET/FETCH for real pagination

Since SQL Server 2012, OFFSET ... FETCH NEXT ... ROWS ONLY provides true offset-based paging — but it requires an ORDER BY clause, unlike LIMIT in the other four dialects. Older SQL Server versions need a ROW_NUMBER() window-function workaround instead.

OFFSET/FETCH pagination

SELECT id, title
FROM posts
ORDER BY published_at DESC
OFFSET 40 ROWS FETCH NEXT 20 ROWS ONLY;

Why ORDER BY matters more than it looks

Without an ORDER BY on a unique or near-unique column, none of these five dialects guarantees that "page 2" is a stable, non-overlapping set of rows — the database is free to return rows in any physical order it finds convenient, which can duplicate or skip rows between two otherwise-identical paged requests, especially under concurrent writes.

Quick reference

PostgreSQL — LIMIT n OFFSET m

MySQL — LIMIT n OFFSET m, or LIMIT m, n (offset, count)

SQLite — LIMIT n OFFSET m

SQL Server (T-SQL) — TOP (n) for a cap; OFFSET m ROWS FETCH NEXT n ROWS ONLY for real paging (ORDER BY required)

BigQuery — LIMIT n OFFSET m

You can paste any of the snippets above into sqlfmt and switch the dialect dropdown to see how each one formats.

SQL Pagination Across Databases: LIMIT, TOP, and OFFSET-FETCH Compared

Quick answer

FAQs

Does SQL Server support LIMIT?

Why does my MySQL LIMIT return the wrong rows?

Does OFFSET/FETCH need ORDER BY in SQL Server?

Is pagination deterministic without ORDER BY?

Does BigQuery support OFFSET?

The Comprehensive Guide to SQL Data Types: Storage, Precision, and Cross-Dialect Portability

The Definitive Guide to SQL Window Functions: Syntax, Framing, and Real-World Recipes

The Ultimate Guide to SQL JOINs: Visualizing Every Join Type, Cardinality, and Performance

Key takeaways

PostgreSQL, MySQL, SQLite, and BigQuery: LIMIT and OFFSET

SQL Server: TOP for a simple cap

Why ORDER BY matters more than it looks

Quick reference

Quick answer

FAQs

Does SQL Server support LIMIT?

Why does my MySQL LIMIT return the wrong rows?

Does OFFSET/FETCH need ORDER BY in SQL Server?

Is pagination deterministic without ORDER BY?

Does BigQuery support OFFSET?

Keep reading

The Comprehensive Guide to SQL Data Types: Storage, Precision, and Cross-Dialect Portability

The Definitive Guide to SQL Window Functions: Syntax, Framing, and Real-World Recipes

The Ultimate Guide to SQL JOINs: Visualizing Every Join Type, Cardinality, and Performance

Key takeaways

PostgreSQL, MySQL, SQLite, and BigQuery: LIMIT and OFFSET

SQL Server: TOP for a simple cap

SQL Server: OFFSET/FETCH for real pagination

Why ORDER BY matters more than it looks

Quick reference

Related reading