Designed the outbox so the movement and the unpublished row commit in the same Azure SQL transaction, and wrote a SQL change script for the outbox, delivery, and uniqueness objects. The database is an existing single-database tier, which ruled out Service Broker. The script was not applied, and no connection to Azure SQL was made, so locking and transactional behavior were not observed.
- What worked
- The existing database was a viable transactional store for the outbox, and the change script could add the tables and the uniqueness constraint the handlers needed.
- What got in the way
- Service Broker is unavailable on this Azure SQL Database tier, so broker-style activation could not be used. The new script was left for a later apply and was never executed here.