How would you reason about database command timeouts in an ASP.NET Core API?

Query timeouts and command timeouts

Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I set a database command timeout that fits the endpoint's response budget and pass the request cancellation token to EF Core operations. A connection timeout limits opening a connection, while a command timeout limits command execution; request cancellation reflects the caller leaving or the API ending the request. If normal list queries hit the command timeout, I inspect generated SQL, execution plans, indexes, row counts, and blocking instead of simply raising the value.

Full answer below

Practice focus

Understanding of database command timeouts, EF Core/SQL behavior, API boundaries, production risks, and practical debugging or design judgment.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
A database command timeout bounds how long a command may execute; it is distinct from connection timeout and request cancellation. It protects capacity, but it does not explain why the command was slow or guarantee that a timed-out write had no effect.
I set a database command timeout that fits the endpoint's response budget and pass the request cancellation token to EF Core operations. A connection timeout limits opening a connection, while a command timeout limits command execution; request cancellation reflects the caller leaving or the API ending the request. If normal list queries hit the command timeout, I inspect generated SQL, execution plans, indexes, row counts, and blocking instead of simply raising the value.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Timeouts should match the workload. An interactive endpoint may need a short predictable budget, while a report that legitimately runs for minutes belongs in a background job with durable status rather than holding an HTTP request and database connection. I check lock waits, parameter-sensitive plans, connection-pool pressure, and whether retries multiply the total elapsed time. For writes I treat a timeout as a potentially unknown outcome and use idempotency or reconciliation rather than repeating the command blindly.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Treating database command timeouts as a syntax detail instead of a production behavior.
Not checking generated SQL, query plans, or actual data volume.
Testing only with tiny local data and assuming production will behave the same.
Fixing symptoms with caching, timeouts, or retries before understanding the data-access cause.

How would you reason about database command timeouts in an ASP.NET Core API?

Practice focus

Answer path

Why this question matters

Review signals

Coding practice

Follow-up prompts

Continue the section

Tech stacks

Skill areas

Suggest an improvement