ORM – the tip of an iceberg
summary
Covers how using ORMs (like Entity Framework) hides important SQL Server features and can lead developers to avoid the database layer; demonstrates several often-overlooked SQL Server capabilities and shows concrete ways to access some of them from Entity Framework to leverage database power without leaving the ORM entirely.
AI-written summary · about
chapters (15)
- 0:00ORM introduction
- 3:40In-memory vs database report
- 8:22Disabling ORM change tracking
- 13:00ORM and mikroORM explained
- 16:56ORM for simple cases
- 21:44Sensitive data masking
- 25:00Data separation in multi-user apps
- 29:41Database versioning
- 35:05Table normalization and partitioning
- 38:19Indexes and query scans
- 41:49JSON in relational databases
- 43:33Advanced data structures
- 46:02SQL vs ORM in business logic
- 47:51SQL knowledge importance with ORM
- 49:14Summary and Q&A
related talks
41mWhy Should I Know SQL and Databases When I Have an ORM?
36mORM is an Offensive Anti-Pattern
30mSimplifying Data Access: ORMs for Web Development with JS and TS
52mThe SQL inside the ORM/Builder box | Claudio Zizza
46mBeyond Good and ORMs
45m.NET: SQL vs ORM - Will Dapper Resolve the Age-Old Debate?
01h 05mAdvanced Weapons and Tactics
23mI Would Never Use an ORM
