On my current project, we are making use of SQL 2005’s ability to write stored procedures in C#. I went to configure a SQL send adapter to call one of the CLR sprocs, and was suprised to find I could not call it! It turns out, BizTalk is not able to call CLR procedures, unfortunately. As a work-around, we created a wrapper procedure in good-old T-SQL, which in turn calls the CLR sproc. Not the most elegant solution, but it worked in our scenario….
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