Unfortunately there is no way to avoid updating specific objects on the target database as this goes against the ethos of what DB Ghost is trying to do - all objects should be updated to match the source code, if some are ignored then the process is broken in terms of assuring that a target DB matches a baselined set of source code.
Can you shed any more light on your situation, maybe we could suggest an alternative approach?
However the version 5 GUI has a “Question each change before synchronising or applying to the SQL delta” option. This is really only needed when your change control process lets you down.
It is always better (my view only) if you have a specific change to deliver you should ideally create a specific baseline for a schema in that exact condition. So you have it in stone and can always compare sync with reference to it in the future. Trying to track which changes from a delta went where is a tricky path.
Ok, i have more details. We have an application that is using this database. The application is used by several clients, that should have particular tables (different from one client to another). So, this particular tables should remain unaltered after running DBGhost. Thank you very much for support.