I have a table with a varchar(max) field (stored in Dedicated Pool, which is a data source). and it won’t come through to ADLS Gen2 (ODX, version 6284.1). I’m using the Azure Synapse provider.
The longest field contains almost 4 million characters, but I’ve been unable to figure out whether this is a limitation in TX or Azure. Does anyone know?
Best answer by Christian Hauggaard
View original
+7
Hi
it may be a limitation - I do not know whether PolyBase is used in your scenario but having 1MB limitations on LOB data is fairly common in this field. A varchar(max) will store a pointer in the record (there are usually also limits in record size as well) to the actual data. Do you get an error or a timeout? I guess TimeXtender may be able to confirm.
Hi
There are no error messages in the UI or logs because I load data “on demand”. But your question triggered something I should have thought of … to do a simple ODX load, which I just did … and ran into this one:
System.NullReferenceException: Object reference not set to an instance of an object
We might need
+5
It may be better to add a ticket in the old system for this.
It may be about the size, but we will have to get a similar sized field to replicate the issue.
Thanks
I’ll do that...!.
+5
I replicated the steps described, creating a field varchar(max) on synapse with 4,000,000 characters
After which I received the following error message on the transfer task that "completed with warnings"
I managed to resolve the issue by increasing the connection timeout for the Azure DL storage on my ODX instance in the TimeXtender Portal
I then transferred the table to my MDW and confirmed that the field was brought over in SSMS
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
