Unanswered: what happens if I use SET TRANSACTION READ ONLY and transaction writes to TEMP tables
We have a report engine that does not write to the database.
I would like to use SET TRANSACTION READ ONLY in order for that my transactions would not be assigned an undo segment, in order to save database resources.
But as far as I understand, a readonly transactions can not write to the database, before I use it I would like to verify that such a transaction can write to temporary tablespace (e.g. when need to sort large amount of data).