SQL Server on premises is not dead
summary
Argues that on‑prem SQL Server stays necessary with concrete numbers and failures: a CNC setup reads 1000 Hz over 34 channels and needs under 30 ms so moving to cloud yields 250 ms in Azure and fails real‑time stopping but optimized on‑site tables hit <10 ms response; a legacy sales app makes 200 part lookups causing 2–30 s order times when the DB lives in the US; Entity Framework lazy vs eager loading and GDPR/hospital constraints also determine on‑prem choices.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:09SQL Server still exists on premises
- 7:28On-premises SQL project examples
- 12:44Legacy apps and latency
- 18:06ORM pitfalls and performance
- 23:07Cloud hidden costs
- 26:16Amusement parks need on-prem databases
- 28:43GDPR and cloud data storage
- 34:30Critical systems and machine that goes ping
- 35:58Summary
related talks
50mSQL Server to Azure SQL: Performance and Availability
01h 01mSQL Server in the Cloud - The available options
42mSQL Server on Azure VM - Configuring for price-performance
49mSQL Server on Azure VM - Configuring for Price-Performance
49mSQL Server and Windows Server Better together on Azure
47mPerfecting business continuity for Azure SQL DB
01h 01mLatest Innovations for SQL and Operational Databases for Developers
51mThe 10 things every developer must absolutely know about Azure SQL