I'd like to be able to "tell" the comparison engine that a table exists both in source and in destination databases but has a different name.
This is to avoid objects showing up as "New" on the one side and "Obsolete" on the other side.

e.g. when t_customers has been renamed to t_customer I'd like to be able to match these two sql objects although they appear to have a different name.
Johan Van Hoye
0

Comments

1 comment

  • Andras B
    I'd like to be able to "tell" the comparison engine that a table exists both in source and in destination databases but has a different name.
    This is to avoid objects showing up as "New" on the one side and "Obsolete" on the other side.

    e.g. when t_customers has been renamed to t_customer I'd like to be able to match these two sql objects although they appear to have a different name.

    In our current version of SQL Compare we do not support mapping objects with completely different names. We have introduced experimental support for owner mappings, so you could compare objects with different fully qualified names, but with matching object names (e.g. dbo.mytable with someuser.mytable). I have added your request to our list of features that we consider in our future development.

    Regards,
    Andras
    Andras B
    0

Add comment

Please sign in to leave a comment.