Hello!

I had some queries regarding error handling with SqlBatch.

From my local tests I can observe the following behavior:

1. With default case - SqlBatch.Transaction is null, in case any statement in the batch fails, the changes from non-failing DMLs in the batch get committed.
   QUESTION:
   Is my understanding correct? Does the SqlBatch.Execute* API internally create a local transaction to rollback or commit the changes?

2. If SqlBatch.Transaction is NOT null, and a statement in the batch fails, even the non-failing DML changes are not committed.
   QUESTION:
   Is my understanding correct? Does the provider automatically rollback the changes in case an error is encountered? And will it automatically commit when no errors are there?

Thanks in advance.