Allows you to control the SQL behavior for starting a default
    transaction for a compound statement.

    By default, if there is no current transaction, SQL starts a
    transaction before executing a compound statement or stored
    procedure. However, this might conflict with the actions within
    the procedure, or it might start a transaction for no reason if
    the procedure body does not perform any database access. This
    default is retained for backward compatibility for applications
    which may expect a transaction to be started for the procedure.