Ignore Names of Constraints, Triggers, Bug?

Brian Donahue

Hi William,

SQL Compare should ignore the constraint names as you've described. Do
you have 'Ignore object Order' set in the options as well? I'm fairly sure
that if the indexes are in a different order, it might account for the
reason that you get this difference.

Regards,

Brian Donahue
Red Gate Software Support

"William C. Smith" <wcsmith@comcast.net> wrote in message
news:txipRKTXDHA.1488@server53...
> I am comparing tables between 2 databases using SQL Compare 2.03. I have
> selected the "Ignore Names of Constraints, Triggers" option, but I believe
> that constraint name differences are still showing up.
>
> Please keep in mind that I may not have a complete understanding on how
> constraints are named and maintained in SQL scripts.
>
> Table A difference in green:
> CONSTRAINT [PK__AdHocQueriesCata__1F798287] PRIMARY KEY NONCLUSTERED
> ([queryId])
>
> Table B difference in green:
> CONSTRAINT [PK__AdHocQueriesCata__513AFB4D] PRIMARY KEY NONCLUSTERED
> ([queryId]) WITH FILLFACTOR = 90
>
> Now I understand that the FillFactor is a difference, but I am concerned
> about changing the 513AFB4D and 1F798287 part of the name. Will this screw
> up the target server if the change script is executed? Why is this
> difference still showing up, even if I explicitly chose to ignore it?
>
> Thanks for excusing my ignorance on this!
>
>