LowFile-scopeC# Plug & play

Optimize string column types

Use appropriate column types/lengths (e.g., NVARCHAR(128) vs NVARCHAR(MAX)) for fields with known bounds.

Why this matters

Smaller types improve storage, index efficiency, and query speed.

Side-by-side examples engineers can pattern-match during review.

Avoid

NVARCHAR(MAX) for code/slug fields

Prefer

NVARCHAR(64) for slugs; NVARCHAR(256) for titles

Bad

nvarchar(max) on short codes

Good

nvarchar(64) for short codes

From the same buckets as this rule.

Critical
Block risky database migrations (locking ops, downtime risk)
Review SQL/database migrations for operations that can lock large tables or cause downtime. Examples: creating indexes without CONCURRENTLY (Postgres), ALTER COLUMN TYPE on big tables, adding NOT NULL without backfill, long-running updates without batching. Require an online migration strategy (CONCURRENTLY, backfill in batches, dual-write/expand-contract) and a rollback plan.
migrations-backward-compatdatabase-query-performance
High
Add database indexes for query optimization
Index frequently filtered or joined columns and verify with query plans.
database-query-performanceperformance-efficiency
High
Add database indexes for query performance
Index columns used in WHERE/JOIN/ORDER and enforce uniqueness where applicable.
database-query-performance