

For Azure Synapse we strongly recommend configuring bulk inserts over Azure Blob Storage for best performance, in this case the aforementioned issue is not relevant.


Please note that also Azure SQL Database is affected by this. We will monitor the situation on the Microsoft side and update the driver in Data Virtuality release when the bug gets fixed. setting servers domain name (DN) cert as a connection property support of new. StatementPoolingCacheSize=10 disableStatementPooling=false enablePrepareOnFirstPreparedStatementCall=true Oracle Database 19c and 18c JDBC drivers introduce a new property file. The bug is described hereĪ workaround to this problem exists: if you experience this problem, please add the following parameters to the JDBC properties of the MS SQL data source: We have identified that the root cause for the issue is an open (as of time of writing this article) bug in the Microsoft JDBC Driver. Some customers are reporting bad performance on running INSERTs, SELECT INTOs, replications into MS SQL server while using Microsoft JDBC Driver to connect (rather than the alternative jTDS driver).
