Synchronizing nvarchar(max) columns, data gets truncated

• 
  Hi Gleb,
  
  Thanks for your post!
  
  I have logged a support ticket for you and will email you shortly.

  Anu D June 27, 2016 04:50

  - 0 +
• 
  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.

  jmonix July 29, 2016 16:07

  - 0 +
• 
  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

  David E August 02, 2016 03:48

  - 0 +
• 
  Has there been any progress concerning this bug?
  
  Thank you!

  jmonix September 08, 2016 11:43

  - 0 +
• 
  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

  David E September 12, 2016 03:58

  - 0 +
• 
  thanks for this great post

  zintap September 28, 2016 03:00

  - 0 +
• 
  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

  Mark J November 07, 2016 10:00

  - 0 +

Add comment

Please sign in to leave a comment.