Hi Amelia, thx.
So I figured out what was happening. Apparently a former sysadmin had put in (do not know why you would do this) a task scheduler job in that kills and restarts the SQL Server Agent. The ETL job more times then not would complete before that job would kick off, but if it ran just a few minutes long it would get wacked. So basically the SQL Cancel message was actually spot on, if not helpful on figuring out what was issuing the cancel request. It would be great if somehow the SQL Cancel request could have more information to help track that origin down. Previously I had seen that error on a memory pressure issue where a job would get cancelled due to that. In SQL Server 2017 how do (in transact sql) enable extended events to capture more info. I admit to looking and not quite finding it.
thx
Carl