Limitations of BizTalk Adapter for SQL Server
The following are known limitations for Microsoft BizTalk Adapter for SQL Server:
The SQL adapter does not support synonyms created in the SQL Server database. For information about synonyms in SQL Server, see https://go.microsoft.com/fwlink/?LinkId=120111.
If you change the system time of the computer running the BizTalk Server host, the time is not updated automatically in the BizTalk Server host. This could lead to incorrect behavior of the inbound operations that use the receive port of BizTalk Server. As a workaround, you must restart the host instance that has a receive port after you have changed the system time of the computer running it.
If a parameter name in a stored procedure contains 127 or more characters, you cannot execute the stored procedure using the SQL adapter. This is due to the limitation of ADO.NET.
The WSDL the SQL adapter generates, when converted to a proxy, exposes the DateTimeOffset column as System.DateTime. This data type cannot store time zone information. As a consequence, any date/time value the adapter sends to the proxy will be converted into local time in the .NET application. If you wish to keep the time zone information, you must change the interface of your proxy to use the String type instead of System.DateTime. Then, use XmlConvert.ToDateTimeOffset to create a Sytstem.DateTimeOffset object, which can store the timezone information.