Why should you care?

ShopNest legacy reporting query already tuned by DBA — FromSqlRaw reuses it without rewriting complex LINQ.

See it live — copy this example

Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).

var topProducts = await _context.Products
    .FromSqlRaw(@"
        SELECT p.Id, p.Name, p.Price, p.CategoryId, p.Sku, p.StockQty, p.IsPublished
        FROM Products p
        INNER JOIN (
            SELECT TOP 10 ProductId, SUM(Quantity) AS Units
            FROM OrderItems
            GROUP BY ProductId
            ORDER BY Units DESC
        ) s ON p.Id = s.ProductId")
    .AsNoTracking()
    .ToListAsync();

What happened?

• FromSqlRaw maps result columns to Product properties — must match shape.
• Parameterize with FromSqlInterpolated to prevent injection.

Practice next

1. Prefer FromSqlInterpolated for parameters: $"WHERE CategoryId = {id}".
2. Ensure selected columns match entity properties or use keyless type.
3. Compose LINQ after FromSqlRaw for additional filters.
4. Map keyless TopSellerDto with SqlQuery instead of full entity.
5. Add AsNoTracking after FromSqlRaw for read reports.

Remember

FromSqlRaw runs custom SELECT mapped to entities. Always parameterize user values. Use for DBA-tuned or legacy SQL.

ShopNest bestseller report

Analytics team ships stored SQL for top sellers; API wraps FromSqlRaw.

Outcome: Report matches SSMS benchmark without fragile LINQ translation.