IBM Support

What's new in IBM InfoSphere Data Architect 9.1.2 and 9.1.3

Fix Readme


Abstract

This document describes the improvements that have been made in InfoSphere Data Architect 9.1.2 and 9.1.3.

Content

InfoSphere Data Architect 9.1.2 and 9.1.3:

To view what's new and changed in InfoSphere Data Architect, select a version:

Version 9.1.3

New and Changed Features for InfoSphere Data Architect 9.1.3

  • Database support upkeep
    • Eclipse SDK Uplift to ensure shell sharing with Data Studio, Rational Application Developer and Rational Developer for z/OS
    • Upkeep to latest available versions of DB2 LUW and Z
    • Support for Oracle 12C and SQL Server 2014
      • Only support for Oracle and SQL Server features previously supported
    • Additional support for DB2i V7.2
      • Support for precision with Timestamp columns
      • Create a global variable at the schema level, set value in property view, generate desired DDL and deploy to the target server.
    • Additional support for Teradata
      • Define server character set for columns
      • Suppress LOGGING, NOCOMPRESS
      • Set options on BEFOR JOURNAL/AFTER JOURNAL/CHECKSUM
      • Multi value compression in domain models
  • New Vendor support
    • Cloudant
  • Easier management of large and complex enterprise models
    • Support for mass edits of properties
    • Ease the upgrade of existing models
    • Support multiple schema containers for objects transformed from a logical data model to a physical data model
    • Diagram filtering by multiple names
    • Specify filtering by multiple names
    • Specify tablespace related parameters
    • Support the drag-n-drop operation for the attributes and columns within an entity or a table directly in the data project explorer
  • Import and Export of Constant Mappings
    • Automatically import/export any constant mappings contained within mapping models to and from a csv file using the import/export mapping model wizard
  • Source Control Management enhancement
    • Added Git and Microsoft Team Foundation Server (TFS) support

Version 9.12

New and Changed Features for InfoSphere Data Architect 9.1.2

  • Entity abbreviations can be used in names for keys:
    • When you create a constraint (physical key, alternate key, relationship, generalization) in a logical data model, the default name of the constraint contains an entity name, and that name is carried over to the physical data model. Some databases have a relatively short limit on name length; for example, for Oracle, the limit is 30 characters. To satisfy that limit, you can now specify a short abbreviation for the constraint in the logical model.

      For example, for a primary key, follow these steps to specify an abbreviation:

      1. Create a logical data model.
      2. Create an entity in the logical data model and save the model, for examle: Name: Entity1 Abbreviation: Ent1
      3. Select Window ->Preference -> Data Management -> Naming Standard and click the Logical-Others tab.
      4. In the Primary Key field, click Add Variables… and open the Data Element Naming Standard window. Select the {entityAbbreviation} variable and click OK.
      5. Edit the primary key naming template and specify, for example, Ent1 as the value of {entityAbbreviation}. The result looks like this: Ent1_PK. Click OK.
      6. In the project explorer, right click the entity created in step 2 and select Add Data Object -> Primary Key. The name of the alternate key is automatically set to the default name Ent1_PK.

      The process is similar for alternate key, relationship, and generalization.

      Entity abbreviations can also be displayed in diagrams of your logical model. You can switch the display between the name, label, or abbreviation.

  • User-defined filters are improved in the Data Model Compare editor:
    • You can now add filters to the Data Model Compare editor delta tree based on kind of changes made to model objects. For example, you can hide all changes made to some types of model objects such as entities or show only changes made to other types of model objects. Filters can be added temporarily during a Data Model Compare editor session or permanently in the preference page for Delta Tree Configuration.
  • Shadow tables are supported for DB2 for Linux, UNIX, and Windows 10.5 FP4 and later:
    • Shadow tables are replication-maintained, column-organized materialized query tables (MQTs). Shadow tables handle analysis queries within an online transaction processing (OLTP) environment to accelerate query response. Shadow tables are also known as replication-maintained MQTs in DB2 environments.
  • Additional support for Oracle:
    • Tables with large objects (LOBs) no longer require data partitions:

      Previously, a partitioning table was required for Oracle tables that contain LOBs. That restriction has been removed.

    • New table types:
      • External tables are supported. Oracle external tables are data tables stored externally to the database server.
      • Index organized tables (IOT) are supported.
      • Created global temporary tables are supported.
    • Partitioning support enhancements:
      • New partitioning strategies
        • Interval: an extension of Range partitioning
        • Reference: the same partitioning used by another table
        • System: rows are assigned to a partition by the DML statement that creates the row rather than by the database.
      • Composite partitioning

        Two level partitioning, for example, range partitions with Hash subpartitions

      • Hash partitioning by quantity:

        You can create multiple hash partitions at the same time instead of creating each partition separately.

    • Volumetric support is now available for Oracle.
  • For Postgres databases, additional support for generating ALTER DDL statements:
    • For Postgres databases, an ALTER DDL statement is now generated for the following actions:
      • Changing the tablespace information for tables
      • Adding columns to tables
      • Changing the NOT NULL value of columns
      • Changing the default value of columns
      • Renaming tables
      • Renaming tablespaces
      • Renaming sequences
      • Renaming domains
      • Renaming functions
      • Changing attribute values for a sequence
  • Alternate keys can now persist during transformation from logical to physical data models:
    • When a logical data model is transformed to a physical data model, the alternate key is usually transformed into a unique index or unique constraint. Now you can specify that the alternate key remains persistent and is not transformed.
  • New option for generating DDL for primary keys
    • You can now generate Primary keys within the CREATE TABLE statement. Previously, the CREATE TABLE statement did not create the primary key, so the only option was to follow it with an ALTER TABLE statement that created the key.
  • Cross-model references for logical models are now published to Design Manager:
    • Now, when publishing logical models, cross-model references for parent/child references (by relationships) and supertype/subtype references (by generalizations) between models are created. Also, when you publish models that refer to other models, you can now publish the referenced models at the same time.

[{"Product":{"code":"SS9UM9","label":"IBM InfoSphere Data Architect"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"9.1.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 January 2021

UID

swg21682045

Page Feedback