One of more common concerns among database administrators who consider migrating their estate to Azure SQL Database is their ability to manage efficiently the migrated workloads. In particular, the absence of the SQL Server Agent introduces the challenge of identifying a means to perform ad-hoc and scheduled automated management tasks across multiple databases, such as rebuilding indexes, updating reference data, or collecting customer telemetry.
Fortunately, recently introduced Elastic Database jobs (still in preview at the time of writing of this article) provide a convenient and efficient way to address this concern. Our objective is to describe their basic functionality and implementation steps.
