Ignore system named constraint and index names Not working
mikecare
Posts: 19 Silver 1
in SQL Compare
I have set the options to ignore, then save and then refresh and still get different named constraints
Tagged:
Comments
Are there other differences in the two table definitions? Does this table show as "in both , but different" in the upper comparison grid?
The logic to determine if objects are shown as different or identical in the upper grid is aware of the options you have selected. If you were to select this object to be deployed you should see no change being deployed to the constraint name. If you are seeing changes in the deployment script, we have a bug that we should investigate in more detail.
The lower pane of SQL Compare will show a textual difference between the two objects as they would be returned from SQL Server. This view is not aware of the option you have provided as it performs a naive text comparison. This does seem like one of the cases where we could avoid scripting out the constraint names to avoid this confusion. I'll have a look and see if there are any improvements we can make.
Redgate Software
I just had the same issue, in that I checked 'Ignore constraint and index names' but was still seeing differences which turned out to be system-named constraints. Until I found this thread.
So 'Ignore constraint and index names' should include system-ones by default, maybe even move the 'Ignore System Named Constraint and Index Names' underneath (tabbed in, even) so that it's obviously clear that there are options here.
Riley Waterhouse Limited
Twitter: @kevriley