At the most basic level, I am looking for a way to
1) execute a stored procedure
2) execute a multi-step process that populates multiple database tables
3) executes another stored procedure
on MS SQL Server, as a single transaction. Setting "a very large transaction interval on your database writer" is not really a good answer; it is not a guarantee. See this answer
Technically, step 2 would happen only if the result returned from the stored procedure in step 1 indicated it was safe to. But one step a time; I need to figure this part out before that becomes relevant.
Is there a way to have a database transaction span a workspace, or some subset of it?
See this related question and my comment there.
Note: Getting FME to call a stored procedure was actually pretty straightforward, even for this FME n00b; it is the environment in which it needs to happen (a single transaction) that is proving bothersome.