What are the challenges you face when working across database platforms? Take the survey

exclude coluns in compare command line?

mbinnixmbinnix Posts: 2
edited October 14, 2005 12:09PM in SQL Compare Previous Versions
We routinely prepare a snapshot for schema revisions and use the command line to distribute these to clients. The xml mechanism for specifing command line swithches is brilliant. But.....

As we push changes from the snapshot to the customer's instance of the database, it will drop any columns, triggers or indexes they've added themselves that extend beyond what we provision with the base product.

I'm familiar with useing the exempt switch and regular expression syntax to exempt certain tables from comparison based on their naming pattern. Is there a way to do the same thing at a more granular level to address columns, triggers or indexes? We could coach our customers to use a consistent naming pattern for this sort of thing to simplify administration of it. But we need to address it at this level to avoid a lot of manual script editing. Otherwise we use compare to create a script, then the customer (or our staff) have to edit it to remove the drop commands.

Thanks in advance.


  • Options
    Brian DonahueBrian Donahue Posts: 6,590 Bronze 1

    I'm afraid that the lowest level that you can filter in SQL Compare is the table. Columns, triggers, and indexes are considered part of the table definition, so you cannot ignore them by name using a regular expression.

    There are some atomic setting that will ignore all triggers and indexes
    SQLCOMPARE /o:it,ii
    but there is no way to ignore specific columns.

    Hopefully this doesn't cause too much inconvenience!
This discussion has been closed.