Is this behaviour specific to SQL version?  When run against my SQL 2012 environment, the variable is set to 1, but the table data remains unchanged

Edit: Forget that. User error...

• This reply was modified 4 years, 8 months ago by  coalesceuk. Reason: I'm an idiot

dwain.c Thanks - I will have a read!

Mark Thanks for the fix, which works with my example data.

I've been testing both solutions with my real-world data. Both take about...

dwain.c, the cross apply does remove a lot of the table scans and works in 2005. I find it harder to understand/read what a cross apply is doing just by...

I think I have a solution, and by changing my example data to split one meeting into 2, I can break Mark Cowne's suggestion

IF OBJECT_ID('tempdb.dbo.#EmployeeProject') IS NOT NULL DROP TABLE...

Many thanks for your responses - I've got some things to try now!

dwain.c, I probably didn't explain it too well, and my attempt to anonymise/simplify what I'm really trying to...