You can create data models that define data to extract
and map target data for data management services. You can also create Optim™ relationships and primary
keys to supplement relationships and primary keys in the database.
Working with access definitions Use access definitions to specify the tables,
relationship traversal, and selection criteria for the data you want
to process.
Working with Optim relationships Optim uses
relationships to determine the data to be retrieved from related tables
and relies upon relationships defined to the database, when available.
However, you can also define Optim relationships
to supplement relationships in the database.
Working with Optim primary keys A primary key is the column or columns that
contain values that uniquely identify each row in a table. A database
table must have a primary key for Optim to
insert, update, restore, or delete data from a database table. Optim uses primary keys that are
defined to the database. However, you can also define Optim primary keys to supplement the primary
keys in the database.
Working with table maps Use a table map to define specifications for
correlating source and destination tables of compatible data. You
can map tables that have different names, modify table names, exclude
tables from a process, or include column maps for greater control
over the data.
Working with column maps A column map provides specifications needed
to match or exclude columns from processing in a data management service.
Convert, insert, and load services must reference a table map, which
may reference one or more column maps. You can use a column map to
define data transformations with privacy policies or column map procedures.
Working with physical data models
You can import a physical data model created with IBM® InfoSphere® Data Architect or IBM InfoSphere Discovery
and associate the model with a data store alias.