Leveraging 6th generation NServiceBus on a project with numerous sagas. Currently leveraging both SQL Transport and SQL Persistence.
Over time the refactoring of the system has ended up with 3 distinct types of order processing sagas that have been boiled down to storing the same two columns in the saga data (UserId and OrderId).
There’s no guidance I’ve seen saying that sharing the same saga persistence table isn’t ok. Simultaneously I’ve not seen where it’s exactly said to be kosher either
If #2 is ok, migrating is as simple as moving the SQL rows into the new combined shared saga state table, correct?