Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
PraveenP
Partner - Contributor
Partner - Contributor

Data truncation

Hi Team,
I have a question: when replicating a map on the data in the Transformation tab, does it never change the source length?

for example nvarchar(30) to wstring(30)

Thanks,
Praveen 

Labels (2)
2 Solutions

Accepted Solutions
Dana_Baldwin
Support
Support

Hi @PraveenP 

Columns should always be a compatible size but your example shows a different (but compatible) data type. This can happen based on the source data type, the internal Replicate data type, and the target data type. Please check the documentation on the data types for the source endpoint you are using, it will show you what the internal data type is. Next, check the documentation for the target data type, it will show you how the internal data type is mapped to the target data type that will be used.

Adding and managing source endpoints | Qlik Replicate Help

Adding and managing target endpoints | Qlik Replicate Help

Hope this helps. Let us know if you have questions.

Dana

View solution in original post

deepaksahirwar
Creator II
Creator II

Dear @PraveenP ,

In Qlik Replicate, when you’re transforming data in the Transformation tab, it generally does not change the source length.

However, there are some considerations to keep in mind:

If the transformation involves changing the data type, make sure that the new data type is compatible with the data in that column.
In homogeneous replication tasks (such as Oracle to Oracle), modifying a single table column (by changing the column data type or length for example), will break the homogeneity for the entire table.

If you found our response useful, we kindly ask you to click on “Accept as Solution”. This will aid other users in finding the answer more effortlessly.

Thank you! ‌‌:-)

 

Best Regards,
Deepak

 

View solution in original post

2 Replies
Dana_Baldwin
Support
Support

Hi @PraveenP 

Columns should always be a compatible size but your example shows a different (but compatible) data type. This can happen based on the source data type, the internal Replicate data type, and the target data type. Please check the documentation on the data types for the source endpoint you are using, it will show you what the internal data type is. Next, check the documentation for the target data type, it will show you how the internal data type is mapped to the target data type that will be used.

Adding and managing source endpoints | Qlik Replicate Help

Adding and managing target endpoints | Qlik Replicate Help

Hope this helps. Let us know if you have questions.

Dana

deepaksahirwar
Creator II
Creator II

Dear @PraveenP ,

In Qlik Replicate, when you’re transforming data in the Transformation tab, it generally does not change the source length.

However, there are some considerations to keep in mind:

If the transformation involves changing the data type, make sure that the new data type is compatible with the data in that column.
In homogeneous replication tasks (such as Oracle to Oracle), modifying a single table column (by changing the column data type or length for example), will break the homogeneity for the entire table.

If you found our response useful, we kindly ask you to click on “Accept as Solution”. This will aid other users in finding the answer more effortlessly.

Thank you! ‌‌:-)

 

Best Regards,
Deepak