If you encounter error Msg 15123, Level 16, reading “The configuration option ‘Agent XPs’ does not exist“, you were probably trying to execute EXEC SP_CONFIGURE 'Agent XPs' while advanced options are hidden.
This error is easily fixed.
If you encounter error Msg 15123, Level 16, reading “The configuration option ‘Agent XPs’ does not exist“, you were probably trying to execute EXEC SP_CONFIGURE 'Agent XPs' while advanced options are hidden.
This error is easily fixed.
If you’ve installed the SQL Server Agent extension in Azure Data Studio, you will be able to see a list of SQL Server Agent jobs, as well as create, edit, view history, etc.
But you may be wondering how to delete a job.
If so, read on.
In a previous article about creating a SQL Server Agent job with T-SQL, I demonstrated how to create a job with a single step.
In this article, I’ll show you how to create a job with multiple steps.
If you’ve ever queried the sysjobhistory table in the msdb database, you’ll probably know that the datetime and duration columns are stored as integers.
In particular, when you query this table, the run_date, run_time, and duration columns are returned as integers, which can make it difficult to read.
Below is a query you can use to return this data in an easier to read format.
In this article, I show you how to create a SQL Server Agent job in the Azure Data Studio GUI.
Here, I create a test job that includes one job step and an attached schedule.
When using T-SQL, you can use the sp_add_schedule stored procedure to add a SQL Server Agent schedule.
This procedure creates the schedule, but it doesn’t attach it to any jobs. To attach it to a job, you must use the sp_attach_schedule procedure.
You can also use sp_add_jobschedule to create the schedule and attach it all with the same procedure.
I wrote this post, because it may not be immediately apparent how to find the SQL Server Agent jobs in Azure Data Studio once you’ve installed the SQL Server Agent Extension.
In SSMS, the SQL Server Agent can be hard to miss, but in Azure Data Studio, it can be hard to find!
Or perhaps you’re not even aware that you need the extension, and you may be searching for jobs that simply can’t be found.
Here’s how to locate the SQL Server Agent jobs in Azure Data Studio.
Often the quickest way to get a list of SQL Server Agent jobs is to simply expand the SQL Server Agent node in the SSMS Object Explorer.
But that’s not the only way. And depending on your environment, it might not even be an option. If you don’t have SSMS or a database tool that allows you to see the SQL Server Agent jobs, you may need to use T-SQL instead.
In this article, I present three options for returning a list of SQL Server Agent jobs when using T-SQL.