SQL Server Transport Upgrade Version 3 to 4

TransactionScope

The Transaction scope transaction mode is not available in .NET Core 2.0 because the implementation of SqlConnection does not support enlisting in an ambient transaction.

To run the upgraded project on .NET Core the transport needs to be switched to one of the native transactions modes. Consider using the Outbox to maintain the same exactly-once processing guarantees.

Transaction scope is supposed to be supported by SqlConnection in future versions of .NET Core.

Multi-instance mode

The multi-instance mode has been deprecated in Version 4. NServiceBus topologies with queues distributed between multiple catalogs and SQL Server instances can be migrated using a combination of Transport Bridge and multi-catalog addressing:

  • When communicating with an endpoint that connects to a different SQL Server instance, send messages through a bridge. The multi-instance migration sample demonstrates this approach.
  • When communicating with an endpoint that connects to a different catalog on the same SQL Server instance, send messages directly and configure multi-catalog addressing.

Both of these features are available for NServiceBus 6 (and SQL Server transport 3.1) so the topology migration can take place before switching to NServiceBus 7.

Related Articles


Last modified