Constraints flagged incorrectly as differences?

Brian Donahue

Hi Chris,

That's right: ignore costratint names was removed from SQL Compare 3. It
will be re-added in a later release.

Regards,

Brian Donahue
Red Gate Technical Support

"Chris Tybur" <ctybur@infinitevisions.com> wrote in message
news:3JhH9SAlDHA.1492@server53...
> My own experience is SQL Server adds those identifiers and they are
> system-dependent. Are your databases on different servers? The way to
> make SQL Compare ignore those kinds of differences is to check the
> option for ignoring constraint names, which is in version 2.X but seems
> to be missing from 3.0.
>
> Chris
>
> Cris McRae wrote:
> > Hello,
> >
> > I have two databases that are pretty much identical, but differences are
> > flagged for constraints, and I'm not sure why:
> >
> > From Database1:
> >
> > [ACDescription] [char] (30) NOT NULL CONSTRAINT
> > [DF__ActivityC__ACDes__0CBAE877] DEFAULT (' ')
> >
> > From Database2:
> >
> > [ACDescription] [char] (30) NOT NULL CONSTRAINT
> > [DF__ActivityC__ACDes__77BFCB91] DEFAULT (' ')
> >
> > Note that the only difference is the seemingly random value 0CBAE877
versus
> > 77BFCB91. Technically the schema of these databases is identical yet
these
> > are flagged as differences, and should not be.
> >
> > Any ideas?
> >
> > Thanks,
> >
> > Cris
> >
> >
>