I have one SQL Agent maintenance job which checks the index fragmentation within a database and rebuilds indexes if required.
This is running well in my test server (Microsoft Sql Server 2012). But my production server is in Azure. Now I want to schedule that job to Azure.
SQL Agent does not exist in Azure SQL Database so how can I schedule a SQL job in Azure DB?
Pre-requisite: we need to have at least one SQL database with a service level objective of S0 or above. To create an elastic job agent, Navigate to the Azure portal and type elastic job in the search box. Select the Elastic Job agents in the list as shown in the below image. On Elastic Job agents page, click on Add.
You can create jobs "manually" by creating batch files and SQL script files, and running them via Windows Task Scheduler. Just put both files into the same folder and exeute the batch file via Windows Task Scheduler.
SQL Agent is not available in Azure SQL Database or Azure Synapse Analytics.
Since this question was first asked, there is now another alternative to handle this problem:
Azure Functions
Here are a couple of examples that could easily be modified to call a stored procedure that rebuilds your indexes
Also see
A few things to keep in mind with Azure functions
Edit September 5, 2021 to add additional information
It should be noted that if you need SQL Agent, you have another option now. I would suggest reading up on Azure SQL Managed Instances. You can see a comparison of Azure SQL to Azure SQL Managed instance here in the Microsoft Documentation. With Azure SQL Managed Instances, your transition to the cloud could be a lot simpler since a lot of the on-premise features you are used to are already there (including SQL Server Agent, DB Mail, etc.).
This feature has been rejected by Microsoft, see here.
To quote the post:
Today in Azure there are several alternatives,
1) SQL Database Elastic Jobs http://azure.microsoft.com/en-us/documentation/articles/sql-database-elastic-jobs-overview/
2) The Azure job scheduler http://www.windowsazure.com/en-us/services/scheduler/
3) The new preview of Azure Automation http://azure.microsoft.com/en-us/services/automation/.
4) SQL Server in a VM
Option 1 requires an additional dedicated cloud service, which increases cost. Option 2 is free (I think) as long as you don't run more than once per hour.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With