Use the Generate DDL tool to create the DDL script used to migrate your DB2 schema objects to your SQL Server database. Each script you create is one DDL task. As with the other HCOSS tools, you name your DDL tasks and store them in a local or shared location.
You can run the Generate DDL tool either from the HCOSS user interface, or from the command line using the
MFDDLConverter
command.
To run the Generate DDL tool, you must have:
- A schema extract file containing schema objects, created using the Extract Schema tool.
- An object transfer list created using the Define Lists tool.
- A connection to your production SQL Server database against which to execute your DDL scripts. Optional if you're using the tool only for the purpose of exporting a DDL script.
- A connection to a test SQL Server database (optional).
The Generate DDL tool includes the following functionality:
- Reads the schema extract file, filtered by the object transfer list that specifies the objects you want to migrate
- Translates the database structure found in the extracted schema and transfer list, including schemas, tables, views, indexes, constraints, and relational information, into a SQL Server 2008 DDL script
- Creates DDL script commands that drop and create objects, or restore missing objects in the SQL Server database
- Maps DB2 data types to SQL Server 2008 data types
- Creates tables using data type mappings defined in the Customize Type Mappings tool
- Enables you to customize DDL at the object level
- Enables you to edit schema mappings
- Tests DDL task specifications against a test SQL Server data source
- Executes generated DDL against your production SQL Server
- Enables you to export the generated DDL as an SQL script
- Reports results of DDL test runs and executions
HCOSS uses DDL tasks in the next step of the database migration process - transferring the data to the SQL database.
Note: HCOSS does not support XML indexes. Therefore, no XML indexes existing in the DB2 database are created in the DDL. Likewise, any column that is part of an index and is mapped to the SQL Server XML data type is not created. This is true even if the originating DB2 index and column are of XML type but are mapped to the XML data type.
