# .NET multi-tenancy: one database per tenant — Part 3/4

Canonical source : [.NET multi-tenancy: one database per tenant — Part 3/4](<https://sebastien.rigaux.be/en/tech-watch/links/net-multi-tenancy-one-database-per-tenant-part-34>)

With one database per tenant, EF Core no longer needs a global query filter, a `TenantId` column, or a tenant-specific model cache key: the tenant is selected through a connection string resolved from a catalog database.

This isolation simplifies the model but shifts complexity to operations: each migration must be applied to every database. The article also explains how `IDesignTimeDbContextFactory` lets `dotnet ef` create the context without an active request or tenant.

- Selected on : 2026-11-02

- Resource publication : 2026-08-20

- Entry updated : 2026-11-07T20:32:37+0000

- Format : Article

- Source language : EN

- Credit : Barret

- Found via : [C\# Digest](<https://csharpdigest.net/>)

Original resource : [.NET multi-tenancy: one database per tenant — Part 3/4](<https://barretblake.dev/posts/development/2026/08/multi-tenant-part-3/>)

Tags : [Multi-tenancy](<https://sebastien.rigaux.be/en/tech-watch/tags/multi-tenancy>) · [.NET](<https://sebastien.rigaux.be/en/tech-watch/tags/dotnet>) · [Entity Framework Core](<https://sebastien.rigaux.be/en/tech-watch/tags/entity-framework-core>) · [Databases](<https://sebastien.rigaux.be/en/tech-watch/tags/databases>) · [Software Architecture](<https://sebastien.rigaux.be/en/tech-watch/tags/software-architecture>)

Available versions : [Français](<https://sebastien.rigaux.be/veille/liens/net-multi-tenant-une-base-par-tenant-partie-34>) · [English](<https://sebastien.rigaux.be/en/tech-watch/links/net-multi-tenancy-one-database-per-tenant-part-34>)

[Back to tech watch](<https://sebastien.rigaux.be/en/tech-watch>)