Multi-Tenant .NET, Part 3: Separate Buildings (Database per Tenant)

Part 3 of 3. Giving every tenant its own database - the strongest isolation there is. It deletes even more code than Part 2 (including the model cache key), and replaces it with a connection-string swap, a catalog database, and the joy of migrating N databases on every deploy.

• dotnet
• ef-core
• sql-server
• multi-tenancy
• architecture

Thursday, August 20, 2026 | 7 minutes Read

Multi-Tenant .NET: Shared Database With Schema Separation

Part 2 of 3. Moving each tenant into its own SQL Server schema — which lets us delete the query filter, the TenantId column, and the SaveChanges stamp from Part 1, in exchange for exactly one new thing: a schema-aware model cache key.

• dotnet
• ef-core
• sql-server
• multi-tenancy
• architecture

Thursday, July 30, 2026 | 7 minutes Read

Multi-Tenant .NET: Shared Database With Partitions

Part 1 of 3. Building a shared-database multi-tenant app in .NET with EF Core global query filters, then using SQL Server table partitioning so the database physically keeps each tenant’s data in its own drawer.

• dotnet
• ef-core
• sql-server
• multi-tenancy
• architecture

Friday, July 17, 2026 | 13 minutes Read