You might want to debatch the document on the incoming pipeline, so that you are mapping a bunch of small messages instead of one huge message. If the performance is bad, you might want to look at using SSIS instead. Bulk loading data into SQL Server is not BizTalk’s strong point. Unless you are getting some other benefit out of using BizTalk here, I would lean toward SSIS.
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name