Describe the suggested improvement
Description
When used with SQL Server transport, the persistence will, by default, try to reuse connections and transactions managed by the transport.
This will happen whether the connection string configured for the persistence matches the transport connections string or not. In such cases, the users might be confused about where their data (e.g. sagas) is stored.
Describe the suggested solution
Validation
Validate if the connection string configured in the persistence matches the one configured for the transport. If the connection strings are different ensure the users calls (to prevent the connection sharing):
var persistence = endpointConfiguration.UsePersistence<SqlPersistence>();
var dialect = persistence.SqlDialect<SqlDialect.MsSqlServer>();
dialect.DoNotUseSqlServerTransportConnection();
Documentation updates
Additional Context
No response