Azure SQL Database - Where is my SQL Agent?
summary
Shows concrete replacements for SQL Agent: linked servers + PowerShell + Windows Task Scheduler to iterate resource groups and collect DB sizes; Azure Automation runbooks that run PowerShell workflows to check index fragmentation and rebuild (demo reduces fragmentation from ~98% to 0%); Azure Functions with Managed Identity to authenticate to Azure SQL and run PowerShell (beware cold-start unless pre-warmed); and Elastic Database Jobs (job DB recommended S1, T‑SQL only, long preview). Notes backups are automatic (35d PITR, 10y LTR) and Managed Instance costs run about 2x compute.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 5:08Challenges in the cloud
- 8:36Overview of solutions
- 10:34Deep dive into runbooks
- 15:01Azure functions and scaling
- 16:43Elastic database jobs
- 20:27Demonstrations and scripts
- 47:51Closing and Q&A
related talks
16mTo Azure SQL Database from SQL Server 2008
50mSQL Server to Azure SQL: Performance and Availability
52mAzure Sql DB Managed instance, a different sql server?
48mThe Kingdom of AdventureWorks Calls for Aid
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
46mBusiness continuity of on-prem SQL Servers using Azure services through Arc
18mHow to reduce your SQL Database costs on Azure
49mOperational insights in your hybrid-cloud multi-cloud SQL inventory outside azure using Arc SQL Serv