It also may seem tempting to be able to queue jobs inside a database transaction. WAAAY back on here I had a good discussion on this problem of writing to the DB and queueing jobs outside or inside a transaction.
Doing it in a transaction is super bad when your job system is in another database. TBH I'm not sure how different it is if the job system is in the same database. I have to assume that holding open a transaction to interact with a very busy table is bad, but I'm not sure.