CA ERwin Data Modeler

Transcription

1 CA ERwin Data Modeler Release Notes r7.3 r Edition

2 This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA ERwin Data Modeler CA ERwin Model Manager

4 Contact CA Technologies Understanding your Support Review support maintenance programs and offerings. Registering for Support Access the CA Support online registration site to register for product support. Accessing Technical Support For your convenience, CA Technologies provides easy access to "One Stop" support for all editions of CA ERwin Data Modeler, and includes the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product For information about other Home Office, Small Business, and Enterprise CA Technologies products, visit Provide Feedback If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is also available on the CA Support website, found at CA ERwin Data Modeler News and Events Visit to get up-to-date news, announcements, and events. View video demos and read up on customer success stories and articles by industry experts.

5 Documentation Changes This Release Notes document is cumulative - it is updated as features are added or changed during the patch and Service Pack releases.the following list summarizes the documentation updates that have been made since the initial release (r7.3 GA) of CA ERwin Data Modeler: Chapter 1: New Features and Enhancements Macro Added (r7.3.5) Addition of the macro DatabaseConnection to the Forward Engineering Template macros. Metadata Integration Bridges Updated (r7.3.2, r7.3.4 SP1, r7.3.8 SP2, and r7.3.11) List of Import/Export bridges added, removed, and renamed. Enhancement made to Rename Column Dialog (r7.3.4 SP1). Allow Special DBMS Characters check box added to the Derive Wizard, Naming Standards pane (r7.3.8 SP2). Functionality was added to Complete Compare to allow export by value of calculated properties. Previously, Complete Compare only exported by state (r7.3.10). Support for Identity columns for DB2 for i was added. You can use the Null Option in the Column Editor to specify the Identity column property (r7.3.10). Changes were implemented to the Display Unified Attributes option in the Advanced Options pane in the Complete Compare wizard (r7.3.11). Additional information about using the Include Only Generated Objects option (Advanced Options pane in the Complete Compare wizard) with indexes was provided (r7.3.11). Chapter 2: System Information Operating System Support - Note added regarding requirement that Administrative privileges are needed when installing, updating, or removing the software. r7.3.8 SP2 includes certification on Microsoft Windows 7 (32-bit only), and Microsoft Windows XP (SP3). Chapter 3: Installation Considerations Silent Install for CA ERwin Data Modeler and Crystal Reports (r7.3.6) Overview and examples for performing a silent install of CA ERwin Data Modeler and Crystal Reports. Chapter 5: Known Issues Known issue with Meta Integration Bridges for Microsoft Office Excel (r7.3.8 SP2) Import and Export issues when working with the Microsoft Office Excel bridges. The silent install is not supported on the Windows 7 operating system.

6

7 Contents Chapter 1: New Features and Enhancements 11 Support for Teradata 2.6/ Model Validation Enhancements for Teradata Integrated SQL Query Tool ODBC-Based Metadata Access Crystal Reports 2008 Included with CA ERwin DM Enhancements to Complete Compare Features Added to Improve Complete Compare Performance with CA ERwin Model Manager Advanced Options Type Resolution Wizard Change to Type Selection Filtering Demand Loading Enhancement Demand Loading and DB Sync Object Selection Enhancement Range Selection Enhancement "Explain" Button Added Template Editor for Forward Engineering Template Files Macro Enhancements Macro Added (r7.3.5) Universal File Close Dialog Enhancements to Open or Save a Model in XML Format Enhancements to Triggers Customize Model Explorer Display Metadata Integration Bridges Updated (r7.3 Initial Release) Import Bridges Added/Removed Export Bridges Added/Removed Bridges Renamed Metadata Integration Bridges Updated (r7.3.2) Import Bridges Added/Removed Export Bridges Added/Removed Bridges Renamed Metadata Integration Bridges Updated (r7.3.8 SP2) Import Bridges Added/Removed Export Bridges Added/Removed Bridges Renamed Metadata Integration Bridges Updated (r7.3.11) Import Bridges Added/Removed Contents 7

8 Export Bridges Added/Removed Bridges Renamed Enhancement to Rename Column Dialog (r7.3.4 SP1) Allow Special Characters During Derive (r7.3.8 SP2) Support for Identity Columns for DB2 for i (r7.3.10) Calculated Properties in Complete Compare (r7.3.10) Display Unified Attributes Option in Complete Compare (r7.3.11) Using the Include Only Generated Objects Option with Indexes (r7.3.11) Database Support Update Databases Removed Databases Added User Interface Changes for Selected Databases Operating System Support Update Integration With Microsoft Visual Studio Team System 2008 Database Edition Metamodel Reference Documentation Compiled HTML Online Help Documentation Bookshelf Feature-Specific Training Videos Chapter 2: System Information 43 Operating System Support System Requirements Supported Target Server Databases Chapter 3: Installation Considerations 45 Installation Wizard on DVD Silent Install for CA ERwin DM and Crystal Reports (r7.3.6) Examples Important Note Installing VSTS Database Edition Chapter 4: General Considerations 49 Metadata Elements Renamed Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler Chapter 5: Known Issues 53 Double-Byte Character Display Known Issue With Meta Integration Bridges for Microsoft Office Excel Silent Install on Windows Release Notes

9 Chapter 6: Documentation 55 PDF Guides New Release Notes PDF Release Numbers Contents 9

10

11 Chapter 1: New Features and Enhancements This chapter of the Release Notes for CA ERwin Data Modeler (CA ERwin DM) documents new features and enhancements for r7.3. This section contains the following topics: Support for Teradata 2.6/12 (see page 12) Model Validation Enhancements for Teradata (see page 13) Integrated SQL Query Tool (see page 13) ODBC-Based Metadata Access (see page 14) Crystal Reports 2008 Included with CA ERwin DM (see page 14) Enhancements to Complete Compare (see page 15) Template Editor for Forward Engineering Template Files (see page 19) Macro Enhancements (see page 19) Universal File Close Dialog (see page 21) Enhancements to Open or Save a Model in XML Format (see page 21) Enhancements to Triggers (see page 22) Customize Model Explorer Display (see page 23) Metadata Integration Bridges Updated (r7.3 Initial Release) (see page 24) Metadata Integration Bridges Updated (r7.3.2) (see page 26) Metadata Integration Bridges Updated (r7.3.8 SP2) (see page 28) Metadata Integration Bridges Updated (r7.3.11) (see page 31) Enhancement to Rename Column Dialog (r7.3.4 SP1) (see page 32) Allow Special Characters During Derive (r7.3.8 SP2) (see page 32) Support for Identity Columns for DB2 for i (r7.3.10) (see page 33) Calculated Properties in Complete Compare (r7.3.10) (see page 33) Display Unified Attributes Option in Complete Compare (r7.3.11) (see page 33) Using the Include Only Generated Objects Option with Indexes (r7.3.11) (see page 35) Database Support Update (see page 38) Operating System Support Update (see page 39) Integration With Microsoft Visual Studio Team System 2008 Database Edition (see page 39) Metamodel Reference Documentation (see page 39) Compiled HTML Online Help (see page 40) Documentation Bookshelf (see page 40) Feature-Specific Training Videos (see page 41) Chapter 1: New Features and Enhancements 11

12 Support for Teradata 2.6/12 Support for Teradata 2.6/12 Support has been added for data modeling with Teradata Version 2.6 and Version 12. Editors have been added for the following objects: Authorization Cast Database File Function Join Index Index (Key Group) Macro Method Permission Profile Replication Group Role Stored Procedure Table (Entity) Trigger User Id View You can access new features in the property editors from the Database menu or from the Model Explorer. Reverse Engineering and Forward Engineering functionality has been updated to support the new properties. Support is not provided for any password or encryption key information in the model. For information about the individual Teradata property editors, see the online help. 12 Release Notes

13 Model Validation Enhancements for Teradata Model Validation Enhancements for Teradata You can create a Model Validation report before you forward engineer your model. The validation process checks for corrupt objects and reports other errors associated with correct forward engineering. A full suite of check model validation routines has been added for Teradata models. In a physical model, from the Tools menu choose Forward Engineering, then Check Model. You can also click the Check Model icon on the Database toolbar. Click F1 in the Model Check dialog for detailed information about the objects and properties that are validated during a model check. Integrated SQL Query Tool The Query Tool provides an easy way to execute SQL SELECT queries against the model or against a database catalog. You can execute a query against the objects and properties in the current model, the metadata defining those objects and properties, and the action log that records the changes that are made to your model during the modeling session. You can create new queries, open existing query files, or paste text from another source (such as a *.sql file) into a query. Sample SQL queries based on the r7.2.x Report Template Builder reports are installed with the product in the \ODBC Reports\RTB Queries folder. Click the Open Query item on the Query Tool toolbar to open a sample report. Each sample report includes a comment summarizing the purpose of the query. For more information on working with the Query Tool, see the ODBC Reporting Guide, which is located in the Doc subdirectory of your CA ERwin Data Modeler installation. You can also open this document from a shortcut on the Start menu. Chapter 1: New Features and Enhancements 13

14 ODBC-Based Metadata Access ODBC-Based Metadata Access CA ERwin Data Modeler r7.3 allows you to use any third-party reporting tool that has ODBC capability to query CA ERwin Data Modeler metadata. For example, you can use queries you created in Excel, Access, Crystal Reports and Cognos and run them against the CA ERwin Data Modeler metadata. At this time only query syntax (SQL SELECT statements) is supported. To enable this functionality, you activate the read-only ODBC-based driver provided with CA ERwin Data Modeler on the Integrations tab of the Options menu. This feature enables open access to the modeling metadata for reporting purposes. This new feature lets you query one model at a time (the current model). Although you cannot query a model in CA ERwin Model Manager, you can query an open model from a mart, if it is the current model. This feature is compliant with ANSI 92 specifications and therefore can be used with any standard ODBC query tool. Crystal Reports 2008 Included with CA ERwin DM Starting with CA ERwin DM r7.3, a licensed copy of Business Objects Crystal Reports 2008 is provided with each copy of CA ERwin DM. The CA ERwin DM install wizard includes an option to install Crystal Reports 2008 edition. With r7.3.6 or later, you can install Crystal Reports using a silent install. See the section on Silent Install under Installation Considerations below. You can use CA ERwin DM as a data source to which you connect via Crystal Reports Two data sources are installed with CA ERwin DM: ERwin - provides the option to select from among open models in the CA ERwin DM workplace ERwin_current - reports on the current model in the CA ERwin DM workplace The option to use Crystal Reports 2008 with CA ERwin DM widens the range of reporting features available to you. The CA ERwin DM metadata schemas are exposed via the data sources, enabling you to craft reports against all the CA ERwin DM metadata including the contents of the Action Log. To help you get started, several sample reports are installed with CA ERwin DM to the \ODBC Reports folder. 14 Release Notes

15 Enhancements to Complete Compare Enhancements to Complete Compare The following enhancements have been added to the Complete Compare functionality. Features Added to Improve Complete Compare Performance with CA ERwin Model Manager New features have been added to maximize performance when working with CA ERwin Model Manager models and Complete Compare. When two different users check out a model from CA ERwin Model Manager, change the model, and check it back in to the mart, the differences display in the Difference Reconciliation dialog (part of the Complete Compare user interface). A conflict exists when two users check the same model out of the mart, and then change the same object or property. When each user checks their models back in to the mart, a "three-way merge" is necessary to reconcile the differences made by each user, and the unchanged objects and properties in the mart. The three-way merge of the models is sometimes slow for large models because all objects participate in the compare process. This compare functionality has changed to reduce the scope of comparison to only objects that have changed for both the local and mart version of the models. The criteria for detecting changes include the following: Objects that have been created in either the local or the mart copy. Objects that have been deleted or modified in at least one of either the local or mart copy. Two new options have been added to the Options dialog available from the Tools menu. The Model Manager tab of the Options dialog now includes the following check boxes: Bypass Difference Reconciliation Dialog if there are no conflicts Select this check box to skip the Difference Reconciliation dialog if no conflicts are detected between the version of the model in the mart and the local version. If no conflicts are detected, the local copy is updated from the mart version before the model is saved. Show All Objects in Difference Reconciliation Dialog Select this check box to turn off the options to optimize the compare process. The Difference Reconciliation dialog will display all objects including those that were not modified in the checked out model and in the mart copy of the model. Note: This feature was first made available with the r7.2.5 SP1 release. Chapter 1: New Features and Enhancements 15

16 Enhancements to Complete Compare Advanced Options Auto-Resolve Missing UDPs Display Unified Attributes Select Active Subject Area Ignore Code Comments Several options have been added to the Advanced pane of the Complete Compare wizard. They are: In some cases, the Type Resolution box appears when Complete Compare detects missing UDPs or property differences for common UDPs. You can select to skip the Type Resolution popup box when all the differences are due to missing UDPs. When you select this check box, all missing UDPs are automatically copied to the target model. This option is not selected by default. Select this check box to simplify the display of foreign-key attributes in the Resolve Differences dialog. When selected, a Unified Attributes group object is used to display all unified attributes (role-named or not) of the same unified set of attributes. Any attributes that are aligned to the attributes under the Unified Group object appear as part of the Unified Group object, even if they are not unified attributes. The Unified Attributes group object carries the unified name if all the attributes under it are part of the same unified set. If not, the name consists of a comma-delimited list of names of all the attributes under it. Specifies that you want to select the active subject area by default in the Object Selection pane. This simplifies the subject area selection, especially in models that contain a large number of subject areas. Select this option to exclude blocks of comments from the body of a trigger, before including it in the compare process. This enables Complete Compare to recognize that a trigger has not changed, if the only difference is in the comment text attached to the trigger. 16 Release Notes

17 Enhancements to Complete Compare Exclude Unaligned Objects/Display Only Aligned Objects Two features on the Advanced Options pane of the Complete Compare wizard enable you to exclude unaligned model-level objects in either the left or right model. They are "Exclude Unaligned Objects in the Left Model" and "Exclude Unaligned Objects in the Right Model". In earlier versions of the product, these options were mutually exclusive - you could not select both. In CA ERwin Data Modeler r7.3 you can now select both check boxes to display only (model-level) aligned objects in the Resolve Differences dialog. These features are useful when you work with a submodel or subject area of a larger model, and then want to compare changes against the larger model. When you select the "Exclude Unaligned Objects..." check box for the larger model, you exclude the model-level unaligned objects from the Resolve Differences dialog display. This results in a more relevant list of differences and a display that is easier to read. Type Resolution Wizard In earlier versions of CA ERwin Data Modeler when the type signatures of the two models were not identical, a popup window displayed, enabling you to review and accept the choices for missing types or type conflicts. In CA ERwin Data Modeler r7.3 this popup dialog has been replaced with a wizard. The wizard makes it easier to navigate and use the available options. Change to Type Selection Filtering In earlier versions of CA ERwin Data Modeler type selection in the Complete Compare wizard resulted in hiding the selected item from the user, not strictly removing the object from the compare process. This resulted in no performance improvement for type filtering. In CA ERwin Data Modeler r7.3 type selection has been updated so that filtering is applied strictly according to the choices made in the Type Selection pane of the Complete Compare wizard. Demand Loading Enhancement When working with a database in Complete Compare, selecting the Allow Demand Loading check box enables you load only the names of the top-level objects from the database catalog. When you perform an action on a partially loaded object in the Resolve Difference dialog, it is fully loaded in order to complete the compare action. In CA ERwin Data Modeler r7.3, demand loading has been optimized to improve overall performance. Chapter 1: New Features and Enhancements 17

18 Enhancements to Complete Compare Demand Loading and DB Sync To optimize performance when doing a DB Sync, the Demand Loading option is now activated by default. In earlier versions, the check box (on the Right Model pane of the DB Sync wizard) was selected by default, but could be changed. In r7.3 you cannot clear this check box. Object Selection Enhancement When a model contains a large number of objects it may be difficult to locate the objects that have been selected in the Right and Left Object Selection panes of the Complete Compare wizard. For example, if you select a Subject Area set, it may be difficult to locate the selected objects in the list. A check box with the label "Hide Unselected Objects" has been added to the Object Selection panes. Select the check box to remove unselected objects from the Selected Objects display. Note: This change also applies to the DB Sync Wizard. Range Selection Enhancement Range selection functionality has been added to the Object Selection panes in Complete Compare. You can now select a range of items on the same level using SHIFT+LEFTCLICK, or select individual items using CTRL+LEFTCLICK. For example, you can use SHIFT+LEFTCLICK to select a range of Entities in the "Selected Objects" list, then clear one check box next to an entity name to clear the check boxes for all the selected entities. In earlier versions of the product, it was necessary to select or clear each check box individually. "Explain" Button Added To improve performance and to make compare results displayed in the Resolve Differences dialog easier to understand, a new "Explain" button has been added to the Resolve Differences dialog. When you click the Explain button, an Explanation dialog opens. For object rows, the text explains why the two objects were aligned. For property rows, the text explains why the two property values are equal. The "Explain" button replaces the "Details" button available in earlier versions of the product. 18 Release Notes

19 Template Editor for Forward Engineering Template Files Template Editor for Forward Engineering Template Files The Forward Engineer wizard now includes a link to a Template Editor, which you can use to view, modify, and create new template files for use with schema generation. The Template Editor features give you a wide range of options for controlling schema generation for your models. You can review and print database-specific features of the default template files, create a custom template file based on a default template file, or create a completely new template file. The Template Editor also includes new macros and extensive customization options. You can access the new Template Editor from within the Forward Engineer wizard, or from an option on the Tools menu. This feature replaces the r7.2.x Database Template option,where you could edit the *.erwin_fe_template files outside the program to modify the schema generation options. The new feature uses *.FET files which you work with using the template editor interface. A technical document, Editing Forward Engineering Templates, is installed with the product in the \Doc folder beneath the folder where you installed CA ERwin Data Modeler. This guide provides an introduction to working with the new template editor. You can also open this PDF from a shortcut on the Start menu. Macro Enhancements This release introduces CA ERwin Data Modeler's Template Language (TLX), the new template/macro language for Forward Engineering templates. The macros available in earlier versions of CA ERwin Data Modeler are still accessible using the Macro Toolbox which you can open from the Domain Dictionary dialog, Model Naming Options dialog, Pre and Post Scripts dialog, Triggers dialog, and so on. A technical document, the Template Language and Macro Reference Guide, is installed with the product in the \Doc folder beneath the folder where you installed CA ERwin Data Modeler. This guide provides extensive technical documentation for the Forward Engineering template macros. You can open help for an individual macro when you right-click the macro name in the Macros pane of the Template Editor. Chapter 1: New Features and Enhancements 19

20 Macro Enhancements Macro Added (r7.3.5) The following macro has been added to the list of r7.3 macros provided in the Forward Engineering Template Editor. Macro Name: DatabaseConnection Description: This macro returns information about the current database connection used by the model. Prototype: Result: DatabaseConnection( Connection Parameter ) Parameter: Connection Parameter Status: Req Description: This identifies the type of information used by the connection. This macro will fail in the following circumstances: The required parameters are not passed in. The model has no target database set. The specified parameters cannot be parsed. The model is not connected to a database. Deprecation Level: Active Sample: [ Connected to database as user DatabaseConnection( User ) ] Result: Connected to database as user User1 20 Release Notes

21 Universal File Close Dialog Universal File Close Dialog The different Close dialogs in earlier releases have been replaced with a "universal" Close dialog to ensure a standardized look and feel throughout the product. When you finish working on a model either locally or from within CA ERwin Model Manager, you can close the current model and continue working on another, or you can close the model and exit. The Close Model dialog also shows the status of the file, such as if it was opened from the server, its lock status, and whether there are unsaved changes. The five model close scenarios are: File/Close from the CA ERwin Data Modeler application menu Service/Close from the CA ERwin Model Manager menu Close model when closing the diagram window File/Exit or Close models when exiting the CA ERwin Data Modeler application Close button in the Complete Compare wizard Note: You must be connected to CA ERwin Model Manager to save a model to the mart. Enhancements to Open or Save a Model in XML Format Changes have been implemented to let you save an XML file in one dialog. In earlier versions of the software, you needed to go through several dialogs to choose the proper XML format. When you select Save As from the File menu, you can select one of the following XML format options as the file type from the Save as type drop-down menu: XML Standard Files (*.XML) Standard XML format does not expand macros or names. This file is suitable for importing back into CA ERwin Data Modeler. XML Standard with Min Info Files (*.XML) Only saves the minimum amount of information needed by CA ERwin Data Modeler to reopen the model. Properties that are derived from other properties or that are read-only are not saved. You can choose to not use this option and still use the standard XML format. XML Repository Format Files (*.XML) The Repository format expands names, macros, and physical names. Derived properties are exported. A file saved in this format cannot be opened with CA ERwin Data Modeler. Chapter 1: New Features and Enhancements 21

22 Enhancements to Triggers Enhancements to Triggers Changes have been implemented to allow you to create model objects for ERwin-generated triggers. In earlier versions of the software, triggers did not exist as objects in the model, they were created during the forward-engineering process but not recognized during reverse-engineering. In CA ERwin DM r7.3, several features have been implemented to allow you to treat triggers as model objects. These enhancements allow you include the triggers in alter scripts, include triggers in Complete Compare scenarios, and associate triggers with model templates. The RI Defaults tab on the Model Properties dialog now includes a check box with the label "Automatically Create RI Triggers". When you select this check box, you are prompted with an option to create RI triggers for existing relationships. The option is then enabled for new objects. If you click No to the prompt, RI Triggers are created only for new relationships. This check box is not selected by default - you must select it to activate this new feature. In the Forward Engineer wizard, on the Options tab for the Triggers object, the wording of the triggers options has been updated to reflect the new distinction between ERwin-generated and User-Defined triggers. When you select to automatically generate RI triggers, a check box is provided with the label "Automatically Generate Missing RI Triggers". The Reverse Engineer - Set Options dialog now includes a check box with the label "Include Generated Triggers". You select this check box to include RI Triggers in the reverse engineer process. 22 Release Notes

23 Customize Model Explorer Display Customize Model Explorer Display Two template files are provided with CA ERwin Data Modeler that let you customize the display of object names in the Model Explorer. By using macros in the template file, you can override the default display of selected object names. The file Logical Names.ont includes display options for the logical model. The file Physical Names.ont includes display options for the physical model. The files are installed to the \Documents and Settings\<user>\Application Data\CA\ERwin Data Modeler\7.3\Templates folder. Comments and a sample macro are provided in the file to customize the display of the parent/child relationship phrase in the Model Explorer. By default, the display is formatted to include the elements <parent name> <relationship name> <child name>. You can modify the macro to exclude one of the elements, for example if you wanted to exclude the parent name in the display. You can add or edit entries in this file to customize the display in Model Explorer. These entries are optional; if there is no macro specified for an object type, the Model Explorer displays the object's name. Note: If earlier versions of CA ERwin Data Modeler these files were named ModelExplorer logical display names.tmpl and ModelExplorer physical display names.tmpl respectively. Chapter 1: New Features and Enhancements 23

24 Metadata Integration Bridges Updated (r7.3 Initial Release) Metadata Integration Bridges Updated (r7.3 Initial Release) The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3 (Initial Release). You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu. The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide. This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product. Import Bridges Added/Removed Support has been added for the following MIMB import bridges: Cognos ReportNet QueryStudio (File) Oracle Business Intelligence Answers Oracle Business Intelligence Enterprise Edition Oracle Business Intelligence Server Oracle Warehouse Builder Sypherlink Harvester 5.x Support has been dropped for the following MIMB import bridges: Ab Initio SA XML Exporter Microsoft SQL Server Analysis Services 7.0 to 9.0 (via DSO) Export Bridges Added/Removed Support has been added for the following MIMB export bridges: CA Repository for Distributed Systems CA Repository for z/os Support has been dropped for the following MIMB export bridges: ASG Rochade (via CWM XMI) Sybase PowerDesigner OOM 9.x to 15.x (via UML XMI) Bridges Renamed IBM Webshere DataStage to IBM InfoSphere DataStage IBM DB2 Data Warehouse Edition/OLAP Acceleration (Cube Views) to IBM InfoSphere Warehouse/Cubing Services for OLAP 24 Release Notes

25 Metadata Integration Bridges Updated (r7.3 Initial Release) IBM DB2 Data Warehouse Edition/Rational Data Architect to IBM InfoSphere Warehouse/Rational Data Architect IBM Rational Rose 98(i) to 2000 to IBM Rational Rose 6.0 (98i) to 6.5 (2000) IBM Rational Rose 2000e to 2003 to IBM Rational Rose 7.x (2000e and newer) Oracle Data Integrator - Beta to Oracle Data Integrator Chapter 1: New Features and Enhancements 25

26 Metadata Integration Bridges Updated (r7.3.2) Metadata Integration Bridges Updated (r7.3.2) The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.2 (Patch Release). You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu. The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.2 Edition). This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product. Import Bridges Added/Removed Support has been added for the following MIMB import bridges: Microsoft Office Excel Advanced Support has been dropped for the following MIMB import bridges: Adaptive Repository & Foundation (via MIR XMI) Adaptive Repository & Foundation (via CWM XMI) Adaptive Repository & Foundation (via UML XMI) Export Bridges Added/Removed Support has been added for the following MIMB export bridges: Microsoft Office Excel Advanced Microsoft SQL Server Integration Services (Project) Support has been dropped for the following MIMB export bridges: Adaptive Repository & Foundation (via MIR XMI) Adaptive Repository & Foundation (via CWM XMI) Adaptive Repository & Foundation (via UML XMI) Bridges Renamed Business Objects Crystal Reports XI (File) to SAP BusinessObjects Crystal Reports XI (File) Business Objects Data Integrator (via CWM XMI) to SAP BusinessObjects Data Integrator (via CWM XMI) Business Objects Designer (File) to SAP BusinessObjects Designer (File) 26 Release Notes

27 Metadata Integration Bridges Updated (r7.3.2) Business Objects Desktop Intelligence (File) to SAP BusinessObjects Desktop Intelligence (File) Business Objects Metadata Manager (via MIR XMI) to SAP Business Objects Metadata Manager (via MIR XMI) CA Gen 4.1a to 7.5 to CA Gen 4.1a to r7.6 Cognos Series 7 Impromptu to IBM Cognos Series 7 Impromptu Cognos ReportNet Framework Manager to IBM Cognos ReportNet Framework Manager Cognos 8 Framework Manager Services to IBM Cognos 8 Framework Manager Services Cognos ReportNet QueryStudio (File) to IBM Cognos ReportNet QueryStudio (File) Cognos ReportNet ReportStudio (File) to IBM Cognos ReportNet ReportStudio (File) IBM Rational Data Architect (RDA) to IBM InfoSphere Data Architect IBM InfoSphere Warehouse/Rational Data Architect to IBM InfoSphere Warehouse/InfoSphere Data Architect Microsoft SQL Server Integration Services to Microsoft SQL Server Integration Services (File) Telelogic Tau (via UML XMI) to IBM Telelogic Tau (via UML XMI) Telelogic (Popkin) System Architect 7.1 to 11x (File) to IBM Telelogic (Popkin) System Architect 7.1 to 11x (File) Telelogic (Popkin) System Architect 10.4 to 11.x (Encyclopedia) to IBM Telelogic (Popkin) System Architect 10.4 to 11.x (Encyclopedia) Chapter 1: New Features and Enhancements 27

28 Metadata Integration Bridges Updated (r7.3.8 SP2) Metadata Integration Bridges Updated (r7.3.8 SP2) The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.8 SP2. You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu. The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.8 SP2 Edition). This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product. Import Bridges Added/Removed Support has been added for the following MIMB import bridges: Borland Together (via UML 2.x XMI) Informatica Developer - Beta bridge IBM Rational Software Architect (RSA) (via UML 2.x XMI) Microsoft SQL Server Analysis Services (via DSV File) Microsoft SQL Server Integration Services (via DSV File) OMG UML 2.x XMI 2.x SAP BusinessObjects Data Integrator Sparx Enterprise Architect (EA) (via UML 2.x XMI) Support has been dropped for the following MIMB import bridges: Microsoft Office Excel (advanced) MicroStrategy 7.0 to 8.1 SAP BusinessObjects Crystal Reports 8.5 to 9.5 (File) SAP BusinessObjects Data Integrator (via CWM XMI) Sun Netbeans XMI Writer Sypherlink Harvester Sypherlink Harvester 5.x Export Bridges Added/Removed Support has been added for the following MIMB export bridges: Database data definition language (DDL) Informatica Developer - Beta bridge Microsoft SQL Server Integration Services (via DSV File) 28 Release Notes

29 Metadata Integration Bridges Updated (r7.3.8 SP2) SAP BusinessObjects Data Integrator Support has been dropped for the following MIMB export bridges: Embarcadero ER/Studio (via ERX) Microsoft Office Access Microsoft Office Excel (advanced) MicroStrategy 7.0 to 8.1 RedHat (MetaMatrix) Enterprise Designer (via MIR XMI) SAP BusinessObjects Data Integrator (via CWM XMI) SchemaLogic SchemaServer (via MIR XMI) Sun Netbeans XMI Writer Unisys ClearPath (via MIR XMI) Bridges Renamed Borland Together (via UML XMI) to Borland Together (via UML 1.x XMI) (Export) CA Component Modeler 4.x (via UML XMI) to CA Component Modeler 4.x (via UML 1.x XMI) (Export) Embarcadero Describe (via UML XMI) to Embarcadero Describe (via UML 1.x XMI) (Export) Embarcadero EA/Studio (via DM1) to Embarcadero ER/Studio Business Architect (via DM1) (Import/Export) Embarcadero ER/Studio to Embarcadero ER/Studio Data Architect (Import/Export) Gentleware Poseidon (via UML XMI) to Gentleware Poseidon (via UML 1.x XMI) (Export) IBM Cognos 8 Framework Manager Services to IBM Cognos 8 BI Reporting - Framework Manager (Import) IBM Cognos 8 Framework Manager Services to IBM Cognos 8 BI Reporting - Framework Manager (Import/Export) IBM Cognos ReportNet Framework Manager to IBM Cognos 8 BI Reporting - Framework Manager for ReportNet (Import) IBM Cognos ReportNet Framework Manager to IBM Cognos 8 BI Reporting - Framework Manager for ReportNet (Import/Export) IBM Cognos ReportNet QueryStudio (File) to IBM Cognos 8 BI Reporting - QueryStudio (Import) IBM Cognos ReportNet ReportStudio (File) to IBM Cognos 8 BI Reporting - ReportStudio (Import) Chapter 1: New Features and Enhancements 29

30 Metadata Integration Bridges Updated (r7.3.8 SP2) IBM Telelogic System Architect 7.1 to 11.x (File) to IBM Rational System Architect 7.1 to 11.x (File) (Import/Export) IBM Telelogic System Architect 10.4 to 11.x (Encyclopedia) to IBM Rational System Architect 10.4 to 11.x (Encyclopedia) (Import/Export) IBM Telelogic Tau (via UML XMI) to IBM Telelogic Tau (via UML 1.x XMI) (Import/Export) Microsoft SQL Server Analysis Services 9.0 (File) to Microsoft SQL Server Analysis Services 2005 to 2008 (File) (Import) Microsoft SQL Server Analysis Services 9.0 (via DSV) to Microsoft SQL Server Analysis Services (via DSV File) (Export) NoMagic MagicDraw (via UML XMI) to NoMagic MagicDraw (via UML 1.x XMI) (Import/Export) Sparx Enterprise Architect (EA) (via UML XMI) to Sparx Enterprise Architect (EA) (via UML 1.x XMI) (Import/Export) Sybase PowerDesigner CDM 8.0 to 12.0 to Sybase PowerDesigner CDM 8.0 to 15.x (Export) Sybase PowerDesigner OOM 9.x to 15.x (via UML XMI) to Sybase PowerDesigner OOM 9.x to 15.x (via UML 1.x XMI) (Import/Export) Tigris ArgoUML (via UML XMI) to Tigris ArgoUML (via UML 1.x XMI) (Import/Export) 30 Release Notes

31 Metadata Integration Bridges Updated (r7.3.11) Metadata Integration Bridges Updated (r7.3.11) The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu. The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r Edition). This guide is available from the Start menu, the bookshelf, or in the \Doc folder where you installed the product. Import Bridges Added/Removed Support has been added for the following MIMB import bridges: IBM InfoSphere Discovery - Beta bridge IBM InfoSphere Discovery (via CWM XMI) Microsoft Office Excel (multi-model) MicroStrategy 7.0 to 9.0 Support has been dropped for the following MIMB import bridges: Oracle Business Intelligence Enterprise Edition Export Bridges Added/Removed Support has been added for the following MIMB export bridges: Meta Integration Business Rules Meta Integration Repository (MIR) XMI Business Glossary Support has been dropped for the following MIMB export bridges: Composite Software Composite Studio (via MIR XMI) Meta Integration Repository (MIR) Transformations to Views XMI file Bridges Renamed Database data definition language (DDL) to Database Data Definition Language (DDL) (Export) Grandite Silverrun-RDM to to Grandite Silverrun-RDM to (Import) IBM Cognos 8 BI Reporting - Framework Manager to IBM Cognos BI Reporting - Framework Manager (Import/Export) Chapter 1: New Features and Enhancements 31

32 Enhancement to Rename Column Dialog (r7.3.4 SP1) IBM Cognos 8 BI Reporting - Framework Manager for ReportNet to IBM Cognos BI Reporting - Framework Manager for ReportNet (Import/Export) IBM Cognos 8 BI Reporting - QueryStudio to IBM Cognos BI Reporting - QueryStudio (Import) IBM Cognos 8 BI Reporting - ReportStudio to IBM Cognos BI Reporting - ReportStudio (Import) Enhancement to Rename Column Dialog (r7.3.4 SP1) In a logical/physical model, if you create column names using domains, you may want to maintain a different name on the logical side (attribute) and physical side (column). A check box has been added to the Rename Column dialog that enables you to break or maintain name inheritance between attribute and column names. For example, in a physical model, you can drag and drop a domain into a table to create a new column. By default, a corresponding attribute is created on the logical side of the model, using the same name. To maintain a unique column name, click Rename in the Column Editor to open the Rename Column dialog, then clear the check box for "Use logical/physical name inheritance". This allows you to alter the physical name without affecting the logical name. Note: An asterisk next to the property name indicates that the value is derived from inheritance. If you do not see the asterisk, the inheritance override check box also is not displayed, indicating that inheritance is not in effect. This option appears in the r7.3.4 (SP1) release and later. Allow Special Characters During Derive (r7.3.8 SP2) An enhancement has been made to the Derive Model Wizard, Naming Standards Tab. The "Allow Special DBMS Characters" check box has been added. This feature only applies when deriving a physical-only model from a logical-only model. When you select the check box you can allow special characters in a physical object name when it is derived from the logical model. This feature enables you to override the restriction on invalid or special characters in physical model object names. See the SQL Reference Documentation for your target server for more information about special characters. Previously, this feature only appeared on the Model Naming Options dialog, Physical tab. 32 Release Notes

33 Support for Identity Columns for DB2 for i (r7.3.10) Support for Identity Columns for DB2 for i (r7.3.10) Support for Identity columns for DB2 for i was added for r You can use the Null Option in the Column Editor to specify the Identity column property. Calculated Properties in Complete Compare (r7.3.10) Functionality was added to Complete Compare to allow export by value of calculated properties. Previously, Complete Compare only exported by state. Calculated properties do not exist in the model. They are calculated based on other properties in the model. Currently when calculated properties are exported, CA ERwin Data Modeler forces the recalculation of the property in the target model. Since the domain or foreign key from which the target property value was calculated remains unchanged, the export looked like it failed. Now Complete Compare allows calculated properties to be exported by value; when a calculated property is exported, a menu displays that lets you choose whether to export the state (existing functionality), or export the value. Note: Once the value of the property is exported, the property breaks its link with the domain or FK level properties from which it inherited its value. Display Unified Attributes Option in Complete Compare (r7.3.11) The Display Unified Attributes advanced option in the Complete Compare wizard was changed in r Chapter 1: New Features and Enhancements 33

34 Display Unified Attributes Option in Complete Compare (r7.3.11) When this option is selected, all lead and non-lead unified foreign key (FK) columns and the corresponding key group members are included in Complete Compare. When this option is not selected, then Complete Compare only includes the lead unified FK column and corresponding key group members. The non-lead unified FK columns and corresponding key group members are not included in the Complete Compare. Example: Two models being compared in the Complete Compare process In the previous example, the columns are not unified in the left model under entity E/3. In the right model the columns are unified under entity E/3. The following example shows the Complete Compare results screen if you did not select the Display Unified Attributes option. There will not be any effect of this selection in the left model as nothing is unified. In the right model, only the unified lead FK column is included in the compare. Here you will see the differences in the columns and key group members of FK and PK; these are valid differences. 34 Release Notes

35 Using the Include Only Generated Objects Option with Indexes (r7.3.11) The following example shows the Complete Compare results screen if you selected the Display Unified Attributes option. Again, there is no difference on the left model as nothing is unified. In the right model, now all of the unified FK columns (lead and non-lead) and corresponding key group members are included in the compare. The unified FK columns show some property level differences, and no differences in the key group members. Using the Include Only Generated Objects Option with Indexes (r7.3.11) Additional information about the Complete Compare advanced option Include Only Generated Objects was provided for r The Complete Compare advanced option Include Only Generated Objects works for indexes only when you use a Database Level Compare. It does not apply for the Logical, Physical, and Logical Physical Level Compare. The following table illustrates the conditions when indexes are filtered in Complete Compare for Database Level Compare with this advanced option selected: Index Generate Generate As Constraint Filtered in Complete Compare PK Not selected Not selected Yes FK Not selected Any value Yes Chapter 1: New Features and Enhancements 35

36 Using the Include Only Generated Objects Option with Indexes (r7.3.11) AK Not selected Not selected Yes IE Not selected Any value Yes Note: In this table, Any value means that the Generate As Constraint option can be selected or not selected. The following table illustrates the conditions when indexes are not filtered in Complete Compare for Database Level Compare with this advanced option selected: Index Generate Generate As Constraint Filtered in Complete Compare PK Any value Selected No PK Selected Any value No FK Selected Any value No AK Any value Selected No AK Selected Any value No IE Selected Any value No Note: In this table, Any value means that the Generate As Constraint option can be selected or not selected. The Indexes are compared in Complete Compare even though the Generate or Generate As Constraint options (or both) are not selected in the Index Editor because you are using the Physical Level Compare. Using the Include Only Generated Objects option has no effect on Indexes except when you use the Database Level Compare. The following illustrations demonstrate this behavior. The FK indexes DONOTGENERATE and XIF1SCN_API_AUD_CNFM_SHMT with the Generate check box not selected appear in the Physical Level Compare and are hidden in the Database Level Compare. Example: Physical Level Compare 36 Release Notes