I'll add some to this. The SharedConnectionWorkflowCommitWorkBatchService can only be used with the out of box SqlWorkflowPersistenceService and SqlTrackingService. The connection strings must be the same (both sets of Sql objects in the same databases). This is intended as a performance enhancement that avoids the overhead of extra connections to the database and DTC transactions.
Important: The SharedConnectionWorkflowCommitWorkBatchService is not about whether or not persistence and tracking will be written transactionally. Regardless of the WorkflowCommitWorkBatchService that you use the services will always use the same transaction (assuming the SqlTrackingService is left in its default IsTransactional=true state; setting this to false will have a completely different write semantic however, see the help docs for more details).
Thanks,
Joel West
MSFTE - SDE in WF runtime and hosting
This posting is provided "AS IS" with no warranties, and confers no rights
|