varbinary being cutoff at 8000

gmoore · Joined: 19 Jul 2011 Posts: 3

I'm having issues when creating a script for a table that that has a column varbinary(MAX). Some of the records has datalength over 8000, after running the script created it's cutting off those records at 8000. I can't find any setting or how to avoid this.

Chris Auckland · Posted: Tue Jul 19, 2011 7:57 pm Post subject:

Thanks for your post.

Is the column varbinary(max) on both the source and the target table?
_________________
Chris

gmoore · Joined: 19 Jul 2011 Posts: 3

Yes.

Thanks

Chris Auckland · Posted: Tue Jul 19, 2011 8:11 pm Post subject:

Ok, I'll test this out. It sounds like a bug.
_________________
Chris

Chris Auckland · Posted: Tue Jul 19, 2011 8:29 pm Post subject:

What version of SQL Data Compare are you using?

I just tried synchronising a VARBINARY(max) column with 36466 characters, and that migrated ok.

Would you be able to send me the DDL for both tables, so I can try and recreate the same project?
_________________
Chris

gmoore · Joined: 19 Jul 2011 Posts: 3

Ok noticed what I did wrong, I modified the key value in the script created but didn't notice it had broken the larger binary rows into blocks of 8000 chars, so the following updates didn't run after the original insert.

Thanks for help.

	All times are GMT + 1 Hour
Page 1 of 1