95 articles · 35 databases · 63 topics
Practical tutorials, performance tuning and internals for SQL Server, PostgreSQL, MySQL, MongoDB, Redis and every engine in between — written by people who run them in production.
Explore by engine
RelationalMicrosoft's enterprise relational database engine.
27 articles →
RelationalThe world's most advanced open-source relational database.
7 articles →
RelationalThe popular open-source database behind much of the web.
7 articles →
RelationalThe long-standing heavyweight of enterprise data.
9 articles →
EmbeddedA tiny, serverless SQL engine inside everything.
5 articles →
DocumentA document database built around flexible JSON-like documents.
6 articles →
Key-valueIn-memory data structures at microsecond speed.
1 article →
Wide-columnMasterless, linearly scalable wide-column store.
3 articles →
Editor's picks
PostgreSQLBeginnerThe index exists, but the plan still shows a scan. Nine common reasons the optimizer can't (or shouldn't) use your index, and how to fix each one.
In this article
· 9 min read
SQL ServerIntermediateSame proc, same code, suddenly 100× slower, and fast again when you run it in SSMS. Here's how parameter sniffing causes it, how to prove it and the fixes that actually hold.
#execution-plans#performance#troubleshooting
SQLiteBeginnerStill getting SQLITE_BUSY with a timeout set? The default timeout is zero and deferred transactions can't wait. WAL mode, busy_timeout and BEGIN IMMEDIATE fix most cases.
#concurrency#locking#troubleshooting
Fresh commits
SQLiteIntermediateAn ordered procedure for SQLITE_BUSY with a verification for each step, a script that reproduces the contention, and the matching settings for Python, Node and Go drivers.
#concurrency#locking#troubleshooting
SQLiteIntermediateWhat SQLITE_BUSY means, where it is returned in rollback-journal and WAL mode, why a timeout sometimes does nothing, the extended codes, and how to find who holds the lock.
#concurrency#internals#locking
GeneralIntermediateAdjacency lists, materialized paths, nested sets and closure tables compared, and why a parent_id column plus a recursive CTE is the right default.
#data-modeling#schema-design
ElasticsearchIntermediateYellow means missing replicas and red means missing primaries. Use the allocation explain API to find the exact cause: replica count, disk watermarks, allocation filters or failed retries.
#configuration#nosql#troubleshooting
Learning paths
LEVEL 01
Tables, keys, joins and your first indexes. Build intuition that lasts.
Browse beginner articles →
LEVEL 02
Query plans, transactions, replication and schema design trade-offs.
Browse intermediate articles →
LEVEL 03
Storage engines, concurrency control, internals and extreme tuning.
Browse advanced articles →
The weekly commit
New tutorials, query-tuning tricks and release notes worth reading — straight to your inbox.
