NServiceBus.Persistence.Sql
NServiceBus.Persistence.Sql copied to clipboard
Performance hit when UPDATE while saga state is unchanged results in updating saga state with same data
When there are no saga state changes we will still do an UPDATE with the saga state
https://github.com/Particular/NServiceBus.Persistence.Sql/blob/9affa576774df39fe4b746409329eb181e1dbab6/src/SqlPersistence/Saga/SqlDialect_MsSqlServer.cs#L71-L78
Unnecessary network IO is spent which will be problematic if the saga state gets large.
Consider implementing "dynamic" updates. Meaning, only include the saga state when changed.