As you might have read earlier (this post), a new SQL Adapter is on its way. The features we plan to support are described there.
Further to that, some time back I had mentioned a few limitations (here), which we wouldn’t be addressing.
I am happy to say that due to the TAP customer feedback received on this feature, we WILL be allowing multiple operations (i.e., INSERT, UPDATE, DELETE on the same or different Tables/Views) as well as Stored Procedure/Function invocations within the same XML message (and therefore, within the same Transaction). One thing to keep in mind though:
- The adapter will only generate the metadata for individual operations (i.e., there will be one schema for INSERT, one for UPDATE, etc, one for a Stored Procedure, etc). The user will manually have to create a schema combining all the operations which need to be a part of the same XML message/Transaction. This shouldn’t be too difficult – once the individual schemas have been generated, coming up with a combined schema should take no more than a couple of minutes. This entire process will be documented.
Our current plan is to release a CTP around the end of May / beginning of June. If you plan on using the adapter, you should join the TAP program. TAP customers have a direct communication channel with the developers on the team, and can play an important role in pushing for important features (important for them) to be included in the final product. If you are interested in joining the TAP program, please leave your email address here (in a comment to this post – don’t worry about spam, I promise to remove your address the moment I make a note of it).