|Elastic Jobs are currently in public preview. The feature is ready and we are preparing to make it officially generally available. No extra steps are required to get started.|
Elastic Jobs is a feature of Azure SQL Database that lets you run a set of T-SQL scripts against a collection of servers or databases, as a one-time job, in an ad-hoc manner, or according to a pre-defined schedule. This feature allows regular maintenance and any action that must be repeated – either across a set of databases or over time, much simpler. Set it up one time, and it will continue to run on any cadence you decide, across any scope you decide, for as long as you wish.
I am releasing a series of posts that will demonstrate and explain the basics of setting up Elastic Jobs to work with a set of databases, including both a General Purpose database and a Hyperscale database. You will understand fundamental concepts needed to properly create Elastic Jobs, how to create, run, and schedule them using PowerShell or T-SQL, as well as some troubleshooting basics.
What are Elastic Jobs?
Elastic Jobs are a powerful tool that can be used to do a variety of automated tasks on a set of Azure SQL servers or Azure SQL databases. The tasks themselves must be things that can be achieved in T-SQL. A sampling of the types of tasks one might choose to achieve includes:
You should consider using Elastic Jobs whenever:
You can target most of the offerings available on Azure SQL Database with Elastic Jobs, this includes:
In my next post, I will cover fundamental concepts that you should understand before beginning to create Elastic Jobs.
This blog is part of a series about Elastic Jobs on Azure SQL Database.
Code samples are also available on GitHub.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.