The Schema Manager allows you to export full or partial database schema to a SQL script file or directly deploy the selected schema objects to a different database or a different server. It also allows to print list of catalog objects from database schema or entire schema SQL scripts for documentation purposes.
For example, you can use it to copy development database schema to your QA environment. Another usage is to take a part of production database schema to development environment to troubleshoot identified production problem. Sometimes it is difficult to export/import database schema, if you want to work only with a subset of application related database objects, which might include some tables, triggers, stored procedures, etc. The Schema Manager allows you to define just a set of objects to copy and can automatically include required dependent objects. For example, if you want to move from production to development database one stored procedure for debugging, the generated SQL script might include all tables, nested stored procedures, views and triggers, which this stored procedure uses. It might make a real difference in case of production databases, which typically have hundreds and sometimes thousands of objects and you need to use just a small subset of them for your application.
It also helps you to re-map DB Spaces and BLOB Spaces when you want to preserve the physical schema layout and fragmentation during the schema migration but the target server has a different spaces.
Schema Print Wizard allows you to define the subset of obejcts to print and a number of options for a printable SQL document generation.