Skip to content

Latest commit

 

History

History
62 lines (42 loc) · 4.52 KB

mapping-db2-schemas-to-sql-server-schemas-db2tosql.md

File metadata and controls

62 lines (42 loc) · 4.52 KB
Raw
title description author ms.author ms.date ms.service ms.subservice ms.topic ms.custom f1_keywords
Mapping DB2 Schemas to SQL Server Schemas (DB2ToSQL)
Mapping DB2 Schemas to SQL Server Schemas (DB2ToSQL)
cpichuka
cpichuka
01/19/2017
sql
ssma
conceptual
sql-migration-content
ssma.db2.schemamappingpanel.f1

Mapping DB2 Schemas to SQL Server Schemas (DB2ToSQL)

In DB2, each database has one or more schemas. By default, SSMA migrates all objects in an DB2 schema to a [!INCLUDEssNoVersion] database named for the schema. However, you can customize the mapping between DB2 schemas and [!INCLUDEssNoVersion] databases.

DB2 and SQL Server Schemas

An DB2 database contains schemas. An instance of [!INCLUDEssNoVersion] contains multiple databases, each of which can have multiple schemas.

The DB2 concept of a schema maps to the [!INCLUDEssNoVersion] concept of a database and one of its schemas. For example, DB2 might have a schema named HR. An instance of [!INCLUDEssNoVersion] might have a database named HR, and within that database are schemas. One schema is the dbo (or database owner) schema. By default, the DB2 schema HR will be mapped to the [!INCLUDEssNoVersion] database and schema HR.dbo. SSMA refers to the [!INCLUDEssNoVersion] combination of database and schema as a schema.

You can modify the mapping between DB2 and [!INCLUDEssNoVersion] schemas.

Modifying the Target Database and Schema

In SSMA, you can map an DB2 schema to any available [!INCLUDEssNoVersion] schema.

To modify the database and schema

  1. In DB2 Metadata Explorer, select Schemas.

    The Schema Mapping tab is also available when you select an individual database, the Schemas folder, or individual schemas. The list in the Schema Mapping tab is customized for the selected object.

  2. In the right pane, click the Schema Mapping tab.

    You will see a list of all DB2 schemas, followed by a target value. This target is denoted in a two part notation (database.schema) in [!INCLUDEssNoVersion] where your objects and data will be migrated.

  3. Select the row that contains the mapping that you want to change, and then click Modify.

    In the Choose Target Schema dialog box, you may browse for available target database and schema or type the database and schema name in the textbox in a two part notation (database.schema) and then click OK.

  4. The target changes on the Schema Mapping tab.

Modes of Mapping

  • Mapping to SQL Server

You can map source database to any target database. By default source database is mapped to target [!INCLUDEssNoVersion] database with which you have connected using SSMA. If the target database being mapped is non-existing on [!INCLUDEssNoVersion], then you will be prompted with a message "The Database and/or schema does not exist in target [!INCLUDEssNoVersion] metadata. It would be created during synchronization. Do you wish to continue?" Click Yes. Similarly, you can map schema to non-existing schema under target [!INCLUDEssNoVersion] database which will be created during synchronization.

Reverting to the Default Database and Schema

If you customize the mapping between an DB2 schema and a [!INCLUDEssNoVersion] schema, you can revert the mapping back to the default values.

To revert to the default database and schema

  1. Under the schema mapping tab, select any row and click Reset to Default to revert to the default database and schema.

Next Steps

If you want to analyze the conversion of DB2 objects into [!INCLUDEssNoVersion] objects, you can Data Migration Report (SSMA Common).

See Also

Connecting to SQL Server (DB2ToSQL)
Migrating DB2 Databases to SQL Server (DB2ToSQL)