Over the past several years, there has been a lack of clarity about Microsoft’s integration roadmap. Various integration tools have been offered, rebranded and renamed, and ultimately retired. With a lack of a published roadmap, it is hard to make an informed investment into an integration platform that needs to meet today’s needs and still be relevant into the future.
Since 2000, BizTalk has been around to meet critical on-premises integration needs. Many customers have implemented complex business-critical solutions based upon BizTalk. With the migration to the cloud and the advent of Integration Platforms as a Service (iPaaS) offerings, there have been concerns about the future of BizTalk and its role in Microsoft’s integration strategy.
A recent announcement by Microsoft’s Jon Fancey, the Azure Integration Services PM Lead, attempts to clear up some concerns about Microsoft’s integration roadmap and lays the foundation for what…
On a recent engagement, I was developing a BizTalk 2013 solution that received XML-based data from several sources and ultimately inserted rows into a SQL Server database using a stored procedure. An additional requirement was that the database connection had to be dynamic.
As with most development, everything worked fine in the development environment and even in initial UAT testing. A timeout issue started to appear intermittently as the size of the data being processed increased and the content of the database grew. Rerunning the same test data through would often complete successfully. The details of the message logged to the Windows Logs was:
A message sent to adapter “WCF-Custom” on send port “WCF.Timeout_126.96.36.199_WCF.Timeout.ProcessDataToSQL_Dyn_WCFTest_c495b1996f35b303″ with URI “mssql://xxxx//Test?” is suspended.
Error details: System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. —> System.ComponentModel.Win32Exception…