Thank you @LaurenzAlbe. What about the order of the read-only transactions though? If "statement 1" sees the results of the "modifying transaction", is a subsequent "statement 2" (in an implicit transaction other than statement 1's) guaranteed to also see the results of the "modifying transaction"? Basically, is there a guarantee of "read consistency" among serial, read-only transactions, such that Read Transaction 2 is guaranteed to see everything that Read Transaction 1 has seen, when Read Transaction 2 strictly "follows" Read Transaction 1?

Well, the error message clearly shows that now LogParser is using the SQL Server Native Client 11.0 driver. As for why the driver's tracing does not show anything, I can't help.