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.
Continue readingIn this article, I present four options for returning SQL Server Agent job history data.
Continue readingIf you get error Msg 15281, Level 16 in SQL Server, chances are you’re trying to run an ad hoc distributed query, but you haven’t enabled ad hoc distributed queries.
This can be fixed easily by enabling ad hoc distributed queries.
Continue readingThis article shows you how to view the history of a SQL Server Agent job in the SQL Server Management Studio (SSMS) GUI.
Continue readingThis article shows you how to view the history of a SQL Server Agent job in Azure Data Studio.
Continue readingOne of the cool things about Azure Data Studio is that you can install extensions to extend its capabilities. One of those extensions is the SQL Server Agent extension.
This extension allows you to do stuff like create jobs, view jobs, view job history, stop/start jobs, etc.
This article shows you how to install the SQL Server Agent extension on Azure Data Studio.
Continue readingIn SQL Server, the sp_help_schedule stored procedure returns information about schedules in the SQL Server Agent.
This article provides an overview of this stored procedure including examples.
Continue readingIn SQL Server, the sp_help_jobschedule stored procedure returns information about the scheduling of jobs.
This article provides an overview of this stored procedure including examples.
Continue readingIn SQL Server, you can use the sp_rename stored procedure to rename an object, including a table.
Most of the other major RDBMs allow you to rename a table with the ALTER TABLE statement, but this isn’t the case with SQL Server.
When you create a SQL Server Agent job with T-SQL, you use the sp_add_jobstep stored procedure to add each job step.
If you ever need to add a new step to that job, you can use sp_add_jobstep once again to add the new job step.
But you may also need to modify the existing step, depending on how you’d like the job to progress through the steps.
Continue reading