We are using DBGhost Plus packages to that create the stand alone database packages we update a customers sites. One our customers added some custom indexes into one our product databases for their own use. We recently ran an database update package at that customer site and they saying that their custom indexes they added are now missing. Question I have is there any options in DBGhust configuration that says to remove indexes in a target database?
There one option we have unchecked under "Comparison setting for objects and data" section which is "Remove everything from the target that doesn't exist in the source (Clean Up)". Is some other option we need to set so it would not drop indexes in target database?
If there are parts of the target schema that you don't 'own' (the bits the customer has added) you can tell DBG compare to ignore them using the partial upgrade screen to enter a regular expression filter.
For example if your customer always names the indexes like this "Custom...." the filter string NOT@Custom will tell the compare code to ignore those indexes.