AllFusion® Data Model Validator Version 4.1.4 SP1 readme

6.0 Contacting Technical Support

1.0 Welcome

Welcome to AllFusion Data Model Validator 4.1.4 SP1 (formally ERwin Examiner). This file presents last-minute product information for AllFusion Data Model Validator version 4.1.4 SP1.

2.0 Installation Considerations

AllFusion Data Model Validator 4.1.4 SP1 is compatible with AllFusion ERwin Data Modeler 4.1 or later.

AllFusion Data Model Validator 4.1.4 SP1 can read ERwin 3.5.2 models as follows:

1. When ERwin 3.5.2 is the only ERwin installed on your machine- AllFusion Data Model Validator 4.1.4 SP1 will default to the ERwin API 3.5.2.

2. When both ERwin 3.5.2 and AllFusion ERwin Data Modeler 4.1.4 SP1 are installed on your machine- AllFusion Data Model Validator 4.1.4 SP1 will default to the AllFusion ERwin Data Modeler 4.1.4 SP1 API, and you can only read models that can be read by AllFusion ERwin Data Modeler 4.1.4 SP1. In order to read ERwin 3.5.2 models, you must go to Tools, Preferences, select the General Settings tab and check Use ERwin 3.5.2 API. AllFusion Data Model Validator will exit. After you restart AllFusion Data Model Validator, the only models you can read are the 3.5.2 models. To reverse this situation follow the same procedure, but this time clear the Use ERwin 3.5.2 API check box.

3.0 General Considerations

3.1 Fixes Provided in Version 4.1.4 SP1

The following issues have been fixed in version 4.1.4 SP1:

• User-defined data types were not being remembered during the parsing process. When this occurred, the software would repeatedly ask if the data type was to be accepted.

• Column diagnostics were flagging user–defined data types as 'Invalid Data Types'.

• Missing indexes were not being reported on deleted relationships.

• The IDENTITY identifier is now saved with a column, but not as a data type.

• Sybase and SQL Server have been separated in the script selections.

• Valid data types are now accepted for all DBMSs.

• If a table with the same PK has a local synonym defined, the software does not ask for the parent when processing same PKs.

3.2 Support for AllFusion® Model Manager 4.1.4 SP1

AllFusion Data Model Validator 4.1.4 SP1 does support AllFusion Model Manager 4.1.4 SP1 (formerly ModelMart^®). There are two ways of reading a model stored in AllFusion Model Manager:

• open the model in AllFusion ERwin Data Modeler and use the Add-in, or

• read the model directly from AllFusion Model Manager in AllFusion Data Model Validator.

3.3 Database Support

The following database systems are supported by AllFusion Data Model Validator 4.1.4 SP1:

• DB2 UDB for z/OS and OS390 versions 4.x, 5.x, 6.x and 7.x (up to version 7.2)

• DB2 UDB for Client/Server version 4.x, 5.x, 6.x and 7.x (up to version 7.2)

• Oracle8i (8.0.5 and 8.1.7) and Oracle9i

• Sybase versions 11.x and 12.x (up to version 12.5)

• SQL Server versions 6.5, 7 and 2000

4.0 Operating System Support

AllFusion Data Model Validator 4.1.4 SP1 minimum hardware requirements:

• 85 MB Hard Disk Space

• 64MB RAM (128MB recommended for large models)

• Microsoft Windows 2003 Server

• Microsoft Windows 2000

• Microsoft Windows XP

• Microsoft Windows Millennium Edition

5.0 Known Issues

5.1 Reverse Foreign Keys in ERwin 3.5.2 Models

AllFusion ERwin Data Modeler obtains foreign key information through the index members of a foreign key. If you reverse the foreign key index, the foreign key will not be reversed. This creates a problem, because AllFusion ERwin Data Modeler reads the index. For example, if the foreign key is based on attributes A, B, C and you change the index of the foreign key to B, C, A, then AllFusion ERwin Data Modeler will read the foreign key as B, C, A. The solution is to maintain the indexes in the same order as the foreign keys inside the ERwin 3.5.2 model.

5.2 Incorrect Diagnostics Count Calculations in the Getting Started Guide

In AllFusion Data Model Validator 4.1, some of the counts in the diagnostics tree were incorrectly calculated. This issue was fixed in version 4.1 Service Pack 2b. However, the screen captures in the AllFusion Data Model Validator 4.1 Getting Started Guide may not agree with the numbers generated when using AllFusion Data Model Validator 4.1.4 SP1 with the DEMO41.er1.

5.3 Updates to Database and Operating System Support

Please refer to this readme file for the latest information about supported databases, and software and hardware requirements for AllFusion Data Model Validator. Previously printed editions of the AllFusion Model Validator Getting Started Guide do not include the latest information about database and operating system support.

6.0 Contacting Technical Support

For further technical assistance with this product, contact Technical Support at http://supportconnect.ca.com for a complete list of locations and phone numbers. Technical support is available 24 hours a day, 7 days a week.