Developer Best Practices for Azure SQL : Avoiding common pitfalls when using the Cloud Database
summary
Covers concrete fixes and demos: implement retry logic and microsoft.data.sqlclient auto-reconnect for transient disconnects, prefer opening connections only for a single query, and use Poly/tenacity where available; send sets not chatty single-row calls (TVPs, JSON, BULK) — a 1,000-row upload goes from 34s -> 0.8s bulk copy in the demo; rely on read committed snapshot default for nonblocking reads, use OUTPUT to return deleted/updated rows in one statement, and use partition switching/truncate partitions to drop large ranges quickly.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:27Resilient Connection
- 3:18Sqlclient
- 4:01Demo
- 22:18Network Latency
- 26:20Using the Recommitted Snapshot
- 26:40Read Committed Snapshot
- 30:47Accelerated Data Recovery
- 31:32Accelerated Database Recovery
- 32:12Avoid Very Long Transaction
- 37:33Load Data into Azure Sql
- 41:28Read the Json File
- 46:54Truncate Table
related talks
51mThe 10 things every developer must absolutely know about Azure SQL
01h 15mChoose Azure SQL Database and Learn What Every Developer Should Know
53mOptimizing your Azure SQL Database workloads
50mSQL Server to Azure SQL: Performance and Availability
56mMigrate Databases to the Cloud - Why, How and Best Practices
49mFrom the Classroom to the Boardroom – Azure SQL DB through Demos
58mFixing poor performance patterns in Azure SQL Database applications
59mLessons Learned from the Trenches: Connectivity and Performance Tips&Tricks
