Avoid duplicate or overlapping indexes

sql

Potential overlap:
INDEX (user_id)
INDEX (user_id, created_at)

The second index may already cover many uses of the first.

Explanation

Review actual query patterns before keeping both. Some overlap is justified, but not all of it.

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Same sheet · prioritizing Anti-patterns

A boolean by itself is often weak unless paired with something else or made partial.

Open In sheetsqlsame section

Unused indexes still hurt writes and consume disk.

Open In sheettextsame section

Rebuild a problematic or bloated index.

Refresh optimizer statistics after big data shifts.

Compact the file after heavy changes when appropriate.