Azure Data Factory Linked Service - Bytes Issue

aboot
Giga Explorer

I'm having a bizzare issue with the ServiceNow linked service within Azure Data Factory, for some reason one paticular table is throwing an error when attempted to perform an incremental extract. I can do a full extract without any issues, however, this is less than ideal with the current throughput (<100KB/s).

 

I am able to incrementally extract from 32 other tables without any problems, it seems to just be isolated to "incident_sla" and to be more precise the "inc_short_description_value" column. This is the following error I am receiving:

 

 

Failure happened on 'Source' side. ErrorCode=UserErrorOdbcOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][DSI] (20039) Cannot store \"ServiceNow\".\"Actual\".\"incident_sla\".\"inc_short_description_value\" value in temporary table without truncation. (Column metadata implied a maximum of 160 bytes, while provided value is 164 bytes),Source=Microsoft.DataTransfer.Runtime.GenericOdbcConnectors,''Type=System.Data.Odbc.OdbcException,Message=ERROR [HY000] [Microsoft][DSI] (20039) Cannot store \"ServiceNow\".\"Actual\".\"incident_sla\".\"inc_short_description_value\" value in temporary table without truncation. (Column metadata implied a maximum of 160 bytes, while provided value is 164 bytes),Source=ServiceNowODBC_sb64.dll

 

 

It implies there's an issue at the source side and that there's a mismatch in length. When doing a full extract, I can see the column is indeed defined as 160 characters (amongst 300k+ rows) - but for some reason there's an attempt to insert a 164 character value in a temporary table before any data transfer occurs when performing an incremental extract. This is the example query which is being submitted:

 

 

SELECT DISTINCT * FROM actual.incident_sla WHERE taskslatable_sys_updated_on_value >= '2023-06-29'

 

 

I'm unfamiliar with the backend of service now, whether there's the ability to change a config setting to enable truncation without throwing an error? I'm at a loss on how to circumnavigate this issue without performing a full extract each day.

 

0 REPLIES 0