Optimizing EF Core Queries When to Use - EF Core queries are slow or generating too many SQL statements - Database CPU/IO is high due to ORM inefficiency - N+1 query patterns are detected in logs - Large result sets cause memory pressure When Not to Use - The user is using Dapper or raw ADO.NET (not EF Core) - The performance issue is database-side (missing indexes, bad schema) - The user is building a new data access layer from scratch Inputs | Input | Required | Description | |-------|----------|-------------| | Slow EF Core queries | Yes | The LINQ queries or DbContext usage to optimize |…