varbinary being cutoff at 8000

Compares and synchronizes SQL database content.

Moderators: Chris Auckland, David Atkinson, richardjm, david connell

varbinary being cutoff at 8000

Postby gmoore » Tue Jul 19, 2011 6:49 pm

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.
gmoore
 
Posts: 3
Joined: Tue Jul 19, 2011 6:41 pm

Postby Chris Auckland » Tue Jul 19, 2011 7:57 pm

Thanks for your post.

Is the column varbinary(max) on both the source and the target table?
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby gmoore » Tue Jul 19, 2011 8:08 pm

Yes.

Thanks
gmoore
 
Posts: 3
Joined: Tue Jul 19, 2011 6:41 pm

Postby Chris Auckland » Tue Jul 19, 2011 8:11 pm

Ok, I'll test this out. It sounds like a bug.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby Chris Auckland » Tue Jul 19, 2011 8:29 pm

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
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby gmoore » Tue Jul 19, 2011 10:41 pm

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.
gmoore
 
Posts: 3
Joined: Tue Jul 19, 2011 6:41 pm


Return to SQL Data Compare Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests