Deploying DB Schema to a different database/server

The Schema Wizard allows you to directly deploy the selected source database objects to a different database or a different server.

The result of this operation is the same as if you would first exported the schema into a script file and then executed this script file from SQL Editor against the target platform.

The advantage of deploying the schema directly are the following:

1. Simplicity. It saves you a few extra manual steps to migrate the schema. It still can generate a script file during this operation if you need it for later use.
2. It allows you to specify run time options, such as if to run the schema within a transaction so that you can rollback changes in case of failure.
3. It allows you to specify the option to skip errors and place error's descriptions in the LOG file. You can later on edit the error log file as a regular SQL script to correct errors and then re-run it. It might save you a lot of time, for example if you successfully deployed several hundred objects and there is one error in one of the stored procedures.
4. You can return to the previous pages of the schema wizard and change object selection or script generation options in case of errors and re-run the deployment operation.
5. If you want to preserve the schema physical layout, such as db spaces and log spaces, you can do it based on the lookup list of spaces from the target server.

To directly deploy generated schema to a different server or a different database just select Deploy to Database option in the target selection panel of the Schema Wizard.