SQLWays (Beta) Web: Schema Mapping

Schema Mapping defines how source schema names are handled and transformed in the generated target code.

Proper schema mapping is an important part of migration projects, especially when migrating to environments with different schema structures, naming conventions, or security models.

In the SQLWays Beta (web based) tool, schema mapping is configured through Options. The following options in the [DDL] section control schema name behavior in the generated target scripts:

• EMPTY_SCHEMA
• OUTSCHEMA

The behavior of schema mapping depends on the combination of these options:

EMPTY_SCHEMA = Yes Schema names are removed entirely, regardless of OUTSCHEMA.

• EMPTY_SCHEMA = Default and OUTSCHEMA=Empty

Default source schemas are removed, while non-default schemas are saved.

• EMPTY_SCHEMA = No and OUTSCHEMA specified

Source schema names are replaced with the value of OUTSCHEMA.

• EMPTY_SCHEMA = Default and OUTSCHEMA specified

Default source schemas are removed, while non-default schemas may be replaced depending on the configuration.

Correctly combining these options allows you to control how schemas appear in the generated target code precisely.

Schema Mapping options allow you to control whether schema names are preserved, removed, or replaced during migration. You can adapt generated scripts to match the target database structure, simplify deployment, and ensure compatibility with existing schemas and environments by configuring EMPTY_SCHEMA and OUTSCHEMA options.

Database Migration Guide

More Tips and Tricks

If you have any questions or face any difficulties, please contact our support team at support@ispirer.com