Error during compare in 5.x

AhimothAhimoth Posts: 4
edited July 24, 2006 3:35PM in SQL Compare Previous Versions
Since I installed SQL Compare 5.x, the comparison of one of my DB's is failing. However versions before 5.x work fine on this database. The error I get happens while creating a comparison project after hitting "Compare Now", it scripts the databases fine, but during the "Comparing" step it stops and says "unexpected char: 0xFFFF". I searched the entirety of syscomments for a binary value of 0xFF, but found nothing in both databases. Is there anyway to pinpoint the source of this error? If not how do I get around it?

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hello,

    Does it still throw the error if you go into SQL Compare's options and ignore extended properties? It's fairly common for vendors to put binary data into an extended property, but SQL Compare seems to want to convert it to a Unicode string.
  • Ahimoth wrote:
    Since I installed SQL Compare 5.x, the comparison of one of my DB's is failing. However versions before 5.x work fine on this database. The error I get happens while creating a comparison project after hitting "Compare Now", it scripts the databases fine, but during the "Comparing" step it stops and says "unexpected char: 0xFFFF". I searched the entirety of syscomments for a binary value of 0xFF, but found nothing in both databases. Is there anyway to pinpoint the source of this error? If not how do I get around it?

    Hi,
    could you send me a screenshot of this error to Andras.Belokosztolszki at red-gate.com please? It would help me to identify which stage the error seems to occur. Also, does this error occur when you compare this database to any other database, or does this occur with a specific combinations of databases?

    Regards,
    Andras
    András Belokosztolszki, PhD
    Red Gate Software Ltd.
  • Email sent with the screenshot. I think I tried turning off extended properties, but I will try again just to be sure.

    Thanks!
  • Yes, it still errors out even after telling it to ignore extended properties.
Sign In or Register to comment.