Scott P. -  Just so I get a better understanding, had the OP used a TRY/CATCH set of blocks, would the cancellation of the query in SSMS have triggered...

Nope, as people have stated about that. In this area, it's your mind that's wrong. NULL ("UNKNOWN") is obviously not...

Agree, NOT(UNKNOWN) cannot be anything apart from UNKNOWN.

It is a mindset thing, and when I write an AND or OR my mind says treat UNKNOWN as FALSE and that works...

It's only an example to get...

Apologies for writing unknown several different ways!

But I don't know the rest, Jeff - what do you mean?

I use stored procedures for ease of amending. But only for more involved queries, and very rarely for the queries that build the SSRS parameter lists of values. The one...

That would actually be easy for me to implement as so happens the proc is a loop - for batch processing with each batch in a transaction. As long as...

Great, thanks both. Should be able to do it now. Want to avoid looking in on Monday morning and finding the job is still running!

Thanks Grant. I presume there are sys tables for jobs and job activity. Not sure if I then do sp_stop_job or KILL process.

Should have added. The job is simply executing a stored procedure.

SELECT 1 SELECT 2

This parses and executes in SSMS with only a space as separator.

How does the parser separate statements when semicolons are not used?

If the semicolon is required for some (new) statements, consistency would mean using it throughout. But we have a mixture and I can't see that changing.

I know that the semicolon...

Thanks.

FROM dbo.tblOrders t

INNER JOIN deleted d ON d.OrderID=t.OrderID

I was thinking it was:

FROM dbo.tblOrders t

LEFT JOIN deleted d ON d.OrderID=t.OrderID

or

FROM inserted i

LEFT JOIN deleted d ON i.OrderID=d.OrderID