If you’re receiving error Msg 3902, Level 16, which reads “The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION”, it’s probably because you’ve got a stray COMMIT statement.
You could be getting this due to implementing error handling, and forgetting that you’ve already committed or rolled back the transaction elsewhere in your code.
Continue readingIn this article, I present four options for using T-SQL to return the schedules that are attached to a SQL Server Agent job.
Continue readingIn 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.
Continue readingWhen 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.
Continue readingOften 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 reading