• Scroll to top of this topic Scroll to Top of Page

  • Print the current topic Print Topic

  • No expanding elements on this page Show/Hide Expanders

Matching Preferences

Specifies matching preferences for all operations in the scenario and cannot be combined with “OpenProject” element.

Use Add element to add a preference for the operation (scenario). It has to be used with the following elements:

Attribute Comment
side Required. Specifies the database for which the preference will be applied. May have the following values: “left”, “source”, “right”, “target”, and “both”. Values “left” and “source” have the same meaning. Values “right” and “target” have the same meaning too. Use the “both” value if you need to set the preference for both sides. Also, use the “both” value if the preference cannot be applied to one side only.
category Optional. Specifies the category for the preference. Used only for Matching Preferences. May have the following values: “Tables”, “Views”, “Functions”, “Procedures”, “Defaults”, “Sequences”, “Packages”, “Rules”, “Synonyms”, “User Defined Types”, “Macroses”, “Operators”, “Shared libraries”, “External tables”.
prefix Optional. Specifies the prefix to ignore of specified category. The default value is an empty string.
suffix Optional. Specifies the suffix to ignore of specified category. The default value is an empty string.

Matching preferences are useful when source and target databases have different naming conventions. For example, all tables in the source database have “_T” suffix (User_T, Order_T …), but the target database does not have suffixes. To enable automatic matching between such databases, specify a preference with a “_T” suffix for tables on source:

<MatchingPreferences>

         <Add side=”source” category=”Tables” suffix=”_T” prefix=”T_” />

</MatchingPreferences>

Matching preferences will be ignored without “category” attribute.