Entity Framework debugging using SQL Server: A Detective Story
summary
Shows how to find slow EF Core LINQ by reading SQL Server: use execution plans to spot a missing index (plan even gives the CREATE INDEX), enable Query Tags (TagWith strings flow as comments so Extended Events link SQL back to the source method), use Query Store for time-series hotspots (enable briefly — ~4% overhead), and apply EF Core 2.2 features: raw interpolated SQL, compiled queries (measured 25–30% faster) and DbContext pooling (~20% faster) for a combined ~35–40% speedup.
AI-written summary · about
chapters (7)
- 0:00Start
- 14:11QUERY TAGS
- 17:03EXTENDED EVENTS
- 23:39SHOW HOW TO ENABLE QUERY STORE
- 31:59STRING INTERPOLATION IN RAW SOL METHODS
- 36:29EXPLICITLY COMPILED QUERIES
- 43:12DBCONTEXT POOLING
related talks
01h 02mUnlocking the Full Potential: The Harmonious Dance of EF Core and SQL Server
01h 00mGetting the best out of Entity Framework Core
01h 04mCommon mistakes in EF Core
01h 01m10 things you didn't know EF Core can do
47mEF Core 6: Working on the Bucket List
01h 04mCommon mistakes in EF Core
01h 05mCommon mistakes in EF Core
49mHow Entity Framework translates LINQ all the way to SQL