Method TryGenerateKeysInAmbientTransactionAsync(int)
Inside a TransactionScope a refill on a connection of its own would be a second connection in the
transaction, and SQL Server refuses the implicit distributed transaction that makes. The range is
reserved through the scope's wrapper instead - on the transaction's connection. A sequence range is
not transactional: a rollback leaves a gap, never a duplicate.
protected override Task<List<long>?> TryGenerateKeysInAmbientTransactionAsync(int count)