Red Gate forums :: View topic - "Ignore Indexes" not working in GUI
Return to RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Compare 10
SQL Compare 10 forum

"Ignore Indexes" not working in GUI

Search in SQL Compare 10 forum
Post new topic   Reply to topic
Jump to:  
Author Message

Joined: 03 Jul 2012
Posts: 23

PostPosted: Fri Jun 28, 2013 3:22 am    Post subject: "Ignore Indexes" not working in GUI Reply with quote


I'm confused.

I'm comparing a single table using the GUI (SVN to DB compare) and I have the following options set:

"Ignore Indexes" = true
"Ignore Constraint Names" = false
"Ignore Check Constraints" = false

In the Results pane, it looks correct: none of the indexes nor the PK are displayed as differences.

In reality, the indexes and PK in SVN are identical to those in the database.

But when I generate the deploy script, the indexes are dropped and the PK isn't touched. When I switch deployment directions, the same thing happens. This behavior seems to be contrary to the options I selected and to the physical state of this table.

The rest of the script is fine.

The only thing I can think that's out of the ordinary is that I've edited this same project a number of times without closing and reopening it. I remapped the table a few times, changed the source and target a few times, switched the deployment direction a few times... Does SQL Compare "cache" stuff or get confused sometimes? I've seen odd behavior like this before that gets cleared up after closing and reopening a project. I haven't posted about it until now, but I'm getting pretty frustrated with it at this point.
Back to top
View user's profile Send private message

Joined: 16 Jun 2010
Posts: 1144
Location: My desk.

PostPosted: Tue Jul 16, 2013 8:38 pm    Post subject: Reply with quote

Thanks for your post, and sorry you're having trouble.

I think to advise fully, we'd really need to see and example of this, as there's a few possibilities.

The ignore options will generally only affect the comparison phase. If there's some other difference on the table (such as a change in column order) which requires the table to be dropped and recreated, then we would do the same with the indexes as part of the process. If you look at the note displayed when you hover over each option, it'll tell you if it affects comparison/deployment or both.

I don't think making changes to the project itself will have an effect- the actions that will be performed are calculated during the compare phase. If you're still stuck, then a more detailed example would be great- you can either post back here or, if you prefer, email support directly with the ticket ref. you obtained originally in the subject line (F00xxxxx)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB © 2001, 2005 phpBB Group