Yes—usually. EF Core generally opens a connection for a database operation and closes it afterward. The underlying database driver, not EF Core, manages connection pooling and may reuse that connection for later work. An EF Core open/close event therefore does not necessarily mean a new physical connection was created and destroyed.
How EF Core connection reuse works
A DbContext represents a unit of work; its lifetime does not require a database connection to stay open for that entire time. EF Core generally opens the connection just before an operation, such as a query, and closes it when the operation finishes. The driver can return the connection to its pool for reuse. Microsoft describes this as the usual behavior, intended to avoid keeping connections out of the pool longer than necessary: Advanced Performance Topics – EF Core.
These are separate events at different layers: EF Core requests that a connection open or close, while the driver decides how physical connections are pooled and reused. Pooling is usually enabled by default, according to Microsoft, but the exact behavior depends on the provider, driver, connection-string identity, pool availability, and server conditions. Reuse is not a guarantee that every operation gets the exact same physical connection.
Connection pooling and DbContext pooling are different
| What is pooled | Who manages it | What it reuses | Configuration |
|---|---|---|---|
| Database connections | The underlying database driver, such as an ADO.NET driver | Eligible database connections | Driver-specific; ADO.NET drivers commonly expose minimum and maximum pool sizes through connection-string settings. Check the installed driver’s documentation. |
DbContext instances |
EF Core, when context pooling is configured | Context objects, reducing allocation and initialization overhead | EF Core context-pool registration and capacity |
Using AddDbContextPool does not itself enable or cause database connection pooling. Connection pooling can be used with pooled or non-pooled contexts; the two mechanisms address different resources and do not imply one another. See Microsoft’s EF Core performance documentation for the distinction.
#1 Best Overall
Does EF Core open a new connection for every query?
EF Core may perform an open/close cycle around each operation, but that is not proof that each query creates a new physical database connection. When pooling is enabled and a suitable connection is available, the driver may reuse one. Avoid interpreting EF-level connection events as evidence that a socket was created or torn down for every query.
Should you keep the connection open?
Not as a general performance optimization. EF Core’s normal pattern is to open the connection for the operation and close it afterward, allowing the driver to return it to the pool. A particular explicit transaction or provider requirement may call for a different lifecycle; follow the driver’s guidance for that case rather than holding a connection open application-wide.
What to do if your code opens a connection manually
Restore the connection to its prior state when your work is finished. In particular, do not assume EF Core will reset arbitrary state changed in the underlying driver when a pooled DbContext is returned for reuse. A manually opened connection left open can carry state into unrelated work. Dispose contexts at the end of their unit of work, and explicitly close manually opened connections when appropriate. See Microsoft’s guidance on pooled contexts and connection state.
How to observe connection lifecycle events
For relational providers, implement an IDbConnectionInterceptor to observe connection creation, opening, closing, and failures. If you only need to observe behavior, use logging or diagnostics rather than interceptor behavior that alters or suppresses operations. Microsoft documents the interceptor API at Interceptors in EF Core.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchConnection reuse does not make a DbContext safe for parallel queries
EF Core does not support parallel operations on the same DbContext instance. Await one operation before starting another on that context, or use separate context instances for parallel work. This is a context concurrency rule, separate from whether the driver reuses database connections. See Microsoft’s DbContext configuration guidance.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
