Synchronizing nvarchar(max) columns, data gets truncated

GlebbyGlebby Posts: 4 Bronze 1
edited November 7, 2016 10:00AM in SQL Data Compare 11
When I synchronize two nvarchar(max) columns, the data in the destination table gets truncated up to 4000 characters. I am using "Deploy using SQL Data Compare" deployment method.

version 11.5.7.1288 professional.

Comments

  • Anu DAnu D Posts: 876 Silver 3
    Hi Gleb,

    Thanks for your post!

    I have logged a support ticket for you and will email you shortly.
    Anuradha Deshpande
    Product Support
    Redgate Software Ltd.
    E-mail: [email protected]
  • I have encountered this identical problem, except I am creating a deployment script. When the data is transferring between the nvarchar(max) columns, a good chunk is getting truncated at the end.
  • Hi Both,

    We have logged this bug as SDC-2176 and are currently investigating. We will update this thread when a fix becomes available.

    David
    Software Engineer
    Redgate Software
  • Has there been any progress concerning this bug?

    Thank you!
  • Hi,

    We have been able to reproduce the issue locally and are currently work towards a fix. We've been rather busy with a number of items with Compare 12 but this is now top of our support list.

    David
    Software Engineer
    Redgate Software
  • thanks for this great post
    Graduated from Soran University with First Class Degree with Honours in Computer Science.
  • Sorry for the delay on this one - it's taken us a while to get fixed, but we've just released 12.0.36.3534 to Frequent Updates with a behaviour change that should prevent this bug.

    We've removed the code that would cause long string rows to get inserted or updated in batches of 8k bytes - now the row will get modified in one go. The old code generally worked fine, but there were edge cases around a combination of non-unique custom comparison keys and custom where clauses where it wouldn't correctly identify the row to update. It appears that this behaviour was working around a bug in Query Analyzer (the 2000 version of SSMS) which we no longer support, so we can simplify the behaviour a bit

    Please let us know if this change fixes your problem :)
Sign In or Register to comment.