How many times to call .SaveChangesAsync() in .BeginTransaction() EF Core 3.1

Question

Call SaveChangesAsync every changes like .Remove , .Update or .Add

using (var transaction = _unitOfWork.BeginTransaction())
            {
                try
                {
                    var structureProfile = await _unitOfWork.StructureProfiles.GetByStructureIdAsync(id);

                    if (structureProfile != null)
                    {
                        _unitOfWork.StructureProfiles.Remove(structureProfile);
                        await _unitOfWork.SaveChangesAsync();
                    }

                    _unitOfWork.Structures.Remove(structure);
                    await _unitOfWork.SaveChangesAsync();

                    await transaction.CommitAsync();
                    return NoContent();
                }
                catch (Exception)
                {
                    await transaction.RollbackAsync();
                    throw;
                }
            }

Or Call SaveChangesAsync() at last part?

using (var transaction = _unitOfWork.BeginTransaction())
        {
            try
            {
                var structureProfile = await _unitOfWork.StructureProfiles.GetByStructureIdAsync(id);

                if (structureProfile != null)
                {
                    _unitOfWork.StructureProfiles.Remove(structureProfile);
                    //await _unitOfWork.SaveChangesAsync(); -- Remove this part?
                }

                _unitOfWork.Structures.Remove(structure);
                await _unitOfWork.SaveChangesAsync();

                await transaction.CommitAsync();
                return NoContent();
            }
            catch (Exception)
            {
                await transaction.RollbackAsync();
                throw;
            }
        }

Answer 1

In your case, with a single method performing the entire unit of work, you don't need the transaction: SaveChangesAsync will perform the actual queries as a single transaction.

Transactions become useful, for example, when the work is spread across multiple methods that each take responsability for their own part of it, including their own SaveChangesAsync . Then, either you explicitly commit the transaction eventually, or you dispose of its object, causing it to be rolled back.