Hello Blasko, Dan W,
Welcome to the Microsoft Q&A forum.
Are you upgraded to the new Salesforce connector?
I don't believe the issue you're facing is due to the integration runtime upgrade. After an internal discussion, it has been confirmed that this behavior is by design.
When auto-creating tables, the SQL sink uses nvarchar(max)
as the default value for non-SQL family source string columns. This is because, when dealing with external data, it is difficult to determine the optimal size for these columns, and using max
ensures that all possible data sizes are accommodated.
Workaround:
use existing table or Implement a pre-copy script that creates the tables with reasonable column lengths before the data is loaded.