A LEFT ANTI SEMI JOIN is a type of join that returns only those distinct rows in the left rowset that have no matching row in the right rowset.
But when using T-SQL in SQL Server, if you try to explicitly use LEFT ANTI SEMI JOIN in your query, you’ll probably get the following error:
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.
Continue readingThe following table contains a list of the date formats that you can provide to the CONVERT() function when you convert a date/time value to a string.
These formats are provided as an optional third argument when calling the CONVERT() function. They’re provided as an integer expression that specifies how the CONVERT() function will format the date.
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 reading