Rider's Built-In Database Tool Window for .NET Development
Stop switching to a standalone SQL client. Rider's bundled database tools can read EF Core connection strings, run migrations, and link SQL to C# entities.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop switching to a standalone SQL client. Rider's bundled database tools can read EF Core connection strings, run migrations, and link SQL to C# entities.
Learn how to optimize EF Core performance by using AsNoTracking to reduce memory overhead and CPU usage in read-only scenarios.
EF Core Global Query Filters let you centralise soft‑delete logic. The filter automatically adds a WHERE clause to every query for a type, eliminating boilerplate and ensuring consistency. Learn how to configure, test, and be aware of common pitfalls.
Use AsSplitQuery to avoid Cartesian duplication when loading several collection navigations in one Entity Framework Core query.
Decide between EF Core split and single queries when using Include: a comparison table, the real trade-offs (round-trips vs row duplication), and how to verify the generated SQL.
Minimal APIs let you expose a full REST service in under 50 lines, cutting boilerplate while keeping ASP.NET Core’s routing, DI, and Swagger. This guide shows a working TODO example, trade‑offs, and when to use them.
Rider can show the SQL your EF Core Take/Skip pagination generates before you run it. Here's how to use that preview to catch full-table scans, N+1 queries, and deep-offset problems early.
EF Core owned types default to required; this diagnostic guide helps you identify why migrations scaffold NOT NULL columns and how to fix them with .IsRequired(false) and verification steps.
EF Core's IAsyncEnumerable streams rows instead of materializing them, but only if you also stop tracking and accept a connection held open for the loop.