PostgreSQL and SQL Server

Database Code Review

Find database performance and migration risks before they reach production.

For engineering leads and agencies shipping a database-heavy feature. Choose one pull request or migration whose correctness, locking behavior or rollout sequence needs a second reading.

What to prepare

Use a sanitized change summary in the enquiry. Include engine/version, approximate affected rows, deployment order and which old application versions may still be running.

After agreement, share the bounded patch or generated SQL through the agreed channel. Repository access and production credentials are unnecessary for initial scoping.

What you receive

  • Prioritized findings with severity and rationale
  • Suggested changes and reproduction guidance
  • Deployment, rollback and validation checks for the agreed patch

Each finding points to the relevant statement, explains the correctness or performance risk, and identifies a test or evidence gap before release.

This review reads a change before it ships. If a database change has already slowed production PostgreSQL, the free snapshot or a slowdown investigation fits better.

Questions the patch should answer

Which statements and plans change?

I review queries, stored procedures, functions and database-related ORM changes alongside the data-access patterns they serve. An index addition can speed a read and add write cost. An index removal needs evidence over a representative workload window.

Who waits during rollout?

For schema migrations and backfills I trace transaction boundaries, lock duration, retry behavior and rollback options. PostgreSQL concurrent index builds and SQL Server index operations have different restrictions. I check the engine version and, for SQL Server, edition before recommending a strategy. See the concurrent index build guide for a PostgreSQL example.

When does a review need production evidence?

If the decision depends on actual wait time, parameter distribution or competing writers, the report names the missing observation. For a wider incident, request a separate PostgreSQL investigation or SQL Server performance review.

Agree the scope before sharing evidence

One agreed database PR or change set at a named revision. One written review and one clarification round. I confirm the fixed fee and delivery window before paid work begins.

Application security audits, infrastructure reviews, unlimited PR reviews and production implementation require a different scope. Static review cannot establish how every change will behave under load.