AllFusion® ERwin® Data Modeler r7.2.9 - Service Pack 2
1.0 Welcome
2.0 Operating System Support
3.0 System Requirements
4.0 Supported Target Server Databases
5.0 Installation Considerations
5.1 Installing the VSTS Database Edition - AllFusion ERwin DM Integration
5.2 Installing API Components
5.3 Requirement for Connecting to SQL Server 2005
6.0 General Considerations
6.1 Enhancements for r7.2.7
6.2 Enhancements for r7.2.8
6.3 Template Files for Customizing Model Explorer Display
6.4 Multiple Constraints on Columns
6.5 Message When Reverse Engineering an Oracle 9i Script
6.6 Sybase CHECK Constraints
6.7 Synchronization Limitation With VSTS Database Edition and AllFusion ERwin DM
6.8 Features Added to Improve Complete Compare Performance with AllFusion Model Manager
6.9 Process to Compare a Local Model and a Large Database
7.0 Known Issues
7.1 Windows Server 2008 and Vista Support for Windows Help
7.2 Limitation with Prefix Owner Feature in Complete Compare
8.0 Published Fixes
9.0 Documentation
9.1 Release Numbers on Documentation
10.0 Contact CA
Welcome to AllFusion ERwin Data Modeler r7.2.9 - Service
Pack 2, a member of the AllFusion Modeling Suite. This file
contains operating system support, system requirements, a
list of supported target server databases, installation
considerations, known issues, documentation notes, and
information about contacting CA Technical Support.
AllFusion ERwin Data Modeler requires that you have one of
the following operating systems installed:
- Microsoft Windows Server 2008
- Microsoft Windows Server 2003
- Microsoft Windows Vista
- Microsoft Windows XP Service Pack 2
- Microsoft Windows 2000
AllFusion ERwin Data Modeler includes integration features
for the following versions of Microsoft Visual Studio:
- Microsoft Visual Studio 2005 Team Edition for Database
Professionals, part of the Microsoft Visual Studio Team
Suite
- Microsoft Visual Studio Team System 2008 Database Edition
(VSTS Database Edition)
The integration also requires that you install the Visual
Studio Power Tools. An option to install the Power Tools is
provided on the last screen of the AllFusion ERwin DM
installation wizard.
The following requirements must be met or exceeded for
AllFusion ERwin DM r7.2.9 - Service Pack 2 to install and
run correctly:
- Intel Pentium III or equivalent
- 400 MB Hard Disk Space
- 1 GB RAM (2 GB recommended for large models)
The following target server databases are supported in
AllFusion ERwin Data Modeler r7.2.9 - Service Pack 2.
- Access (2000/2002/2003)
- DB2 iSeries (5.x)
- DB2/zOS (7, 8)
- DB2/UDB (8.x/9.x)
- FoxPro (stabilized support)
- Informix (7.x, 9.x/10.x)
- Ingres (2.5, 2.6, 2006)
- MySql (5.x)
- ODBC/Generic (2.0, 3.0)
- Oracle (8i, 9.x, 10.x/11.x)
- Progress (8.x, 9.x/10.x)
- Redbrick (stabilized support, 5.x)
- SAS (stabilized support)
- SQL Server (7.0, 2000, 2005/2008)
- Sybase (12.5/15)
- Sybase IQ (12.5)
- Teradata (2.x)
Review the following installation considerations before
installing the product.
When you run setup for AllFusion ERwin DM r7.2.9 - Service
Pack 2, the installation script checks for a copy of
Microsoft Visual Studio 2005 Team Edition for Database
Professionals or Microsoft Visual Studio 2008 Team System
for Database Professionals. If it detects a copy, the
integration components are automatically installed unless
you cancel the selection to install the components. You can
also modify an existing installation of AllFusion ERwin DM
r7.2.9 - Service Pack 2 to add the VSTS Database Edition
integration. See the installation instructions in Chapter 1
of the Integration Guide, provided in PDF format in the
\Doc folder where AllFusion ERwin DM is installed.
The AllFusion ERwin Data Modeler API and two related
components (ERwin SPY, and the ERwin Sample API Client) are
included in the installation when you choose the Complete
Setup Type during setup. If you choose the Custom Setup
Type during setup, you can choose to customize the install
location, and review the space needed to install each
feature.
If you are trying to connect to an AllFusion Model Manager
database which resides on SQL Server 2005 from a machine
that does not have the SQL Server 2000 client installed,
you will not be able to connect to AllFusion Model Manager.
AllFusion Model Manager requires the use of DB-Library for
connecting to SQL Server databases. SQL Server 2005 no
longer distributes the DB-Library files, though DB-Library
is supported for connecting to SQL Server 2005.
In order to be able to connect to an AllFusion Model
Manager database which resides on SQL Server 2005, the file
NTWDBLIB.DLL needs to be installed to the
c:\windows\system32 folder on your workstation. If you have
a SQL Server 2000 installation CD, the SQL Server 2000
client can be installed from the CD by executing
sqlredis.exe located on in the \x86\Other folder. If you do
not have a SQL Server 2000 installation CD, you can find
the file in a directory named "support" on the root of the
AllFusion ERwin DM CD.
This section contains general information you should know
before using AllFusion ERwin Data Modeler r7.2.9 - Service
Pack 2. Enhancements added for r7.2.7 and 7.2.8 are
included in the r7.2.9 - Service Pack 2 product.
The following enhancements were provided with r7.2.7:
- Support was added for Microsoft Visual Studio Team System
2008 Database Edition (VSTS Database Edition). The
Integration Guide (ERwin_VSDB_Int.PDF) was updated and
republished.
- Features were added to improve Complete Compare performance
with AllFusion Model Manager. See the item below for a
detailed description of this enhancement.
The following enhancements were provided with r7.2.8:
Two template files are provided with AllFusion 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 ModelExplorer logical display names.tmpl includes
display options for the logical model. The file
ModelExplorer physical display names.tmpl includes display
options for the physical model. The files are installed to
the default installation directory for the product
(C:\Program Files\CA\AllFusion ERwin Data Modeler r7).
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.
Note: If you modified the template file with build r7.1,
note that the syntax in the files has changed. The
templates no longer use the delimiters "{#" and "#}" to
enclose text.
Support for multiple constraints on columns in SQL Server
2000 or SQL Server 2005 in an AllFusion ERwin DM model is
not currently available.
You may encounter an error message when you reverse
engineer an Oracle 9i script that includes comments that
are not associated with an object. The reverse engineering
process does not create a table for such comments. This
matches the behavior in Oracle, in which properties without
an associated object are not generated in the physical
database.
CHECK constraints are treated differently in Sybase version
12.5 and 12.6/12.7. If you forward engineer a model to a
Sybase 12.5 database, table/column CHECK constraints are
not enforced, so the UNENFORCED keyword is required. If you
forward engineer a model to a Sybase 12.6 or Sybase 12.7
database, CHECK constraints are enforced, so the UNENFORCED
keyword is not required.
AllFusion ERwin DM currently supports Sybase 12.5 syntax.
For later releases, you must edit the DDL for CHECK
constraints to successfully execute on the database.
When you add an AllFusion ERwin DM model to a VSTS Database
Edition project, a connection is established between
AllFusion ERwin DM and VSTS Database Edition. When you save
and close your AllFusion ERwin DM model, your changes are
made to the Visual Studio schema.
A known problem with the Microsoft Visual Studio API
results in certain user objects not being renamed or
deleted from the Visual Studio schema after being renamed
or deleted in the AllFusion ERwin DM model. This applies to
objects that are not owned by the schema, such as user,
database role, partition function, partition scheme, and
the schema itself. If you rename or delete these objects
from a model and save your changes, the objects are not
automatically renamed or deleted in the Visual Studio
project. You must manually delete the instances of these
object types from the Visual Studio Schema View. If you do
not manually modify the Visual Studio schema, the objects
are automatically repopulated into the AllFusion ERwin DM
model the next time you open it in Visual Studio.
This issue will be resolved when an updated API is
available from Microsoft.
New features have been added to maximize performance when
working with AllFusion Model Manager models and Complete
Compare. When two different users check out a model from
AllFusion 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.
With r7.2.8, 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.
Use the following sequence of steps to create a compare
session with a model and a large database. When you use
this process, only database objects that match the objects
selected from the model are loaded from the database. Note
that this process is only relevant when working with
Oracle, SQL Server 2005/2008 and Teradata databases.
In this example, your local model is set as the left model
in the Complete Compare wizard, and the database is set as
the right model.
To compare a local model and a large database
- Open the data model that you want to compare to the
database, then click Complete Compare, Compare on the Tools
menu.
The Complete Compare wizard opens, on the Right Model
Selection pane.
- Click the link for Advanced Options. In the Advanced
Options pane, select the check box for "Exclude unaligned
objects in the right model."
If you wish to filter objects from the left model, select
the links for the Type Selection and Left Object Selection
and work with the filters in those panes of the wizard.
- Load your database as the right model. To do this, click
the link in the Complete Compare wizard for the Right Model
pane, select the "Load from Database/Script" option and
select the Allow Demand Loading option. Click Load.
The Reverse Engineer wizard opens.
- Work with the Reverse Engineer Wizard to select a template
and set reverse engineer options. Click Next in the Reverse
Engineer - Set Options dialog. Enter your database
connection credentials and click Connect.
The reverse engineering process runs, and your database
appears as the "Right Model" in the Complete Compare
Wizard. The compare level, type, and object selections are
reset to their default values. Any filtering of objects in
the left model will be reset.
- Use the options in the Complete Compare Wizard to set the
compare level and filter by objects for either model.
- Click Compare to start the compare process.
The two models are compared, and the Resolve Differences
dialog opens. Your right model only displays objects that
are aligned to the unfiltered objects in the left model.
- Use features in the Resolve Differences dialog to compare
and reconcile any detected differences between the models.
Note: If you move objects or properties into your model
based on the database (the right model) you can generate an
alter script against the database. Click the Right Alter
Script/Schema Generation icon 
to open the Alter Script
wizard.
- Click Finish.
You return to the Complete Compare Wizard. You can change
any options in the wizard and begin the compare process
again, or click Close to close the wizard.
The wizard closes and you return to the main workspace.
Note: An Advanced Option, "Auto-Dispose Database/Script
Models" is selected by default. This means that the model
reverse-engineered from your database is automatically
closed without saving at the end of the Complete Compare
session.
With the release of Windows Server® 2008 and Windows
Vista®, the Windows Help program (WinHlp32.exe) is no
longer included as a component of the Windows operating
system. Third-party programs that include .HLP files are no
longer allowed to redistribute this Windows help program.
However, you can download WinHlp32.exe from the Microsoft
Download Center. For more information about this issue
including download links for your operating system and how
to implement this file, please refer to the following
support document from Microsoft:
http://support.microsoft.com/kb/917607.
The r7.2.x version of the AllFusion Modeling Suite uses
Windows Help. If you install r7.2.x on a new PC running
either Windows Server 2008 or Vista you may have problems
opening the online help. Follow the download instructions
to obtain a copy of WinHlp32.exe from Microsoft and place a
copy of the file in the main folder where you installed the
AllFusion Modeling Suite program files.
When you work with Complete Compare, you can select the
"Prefix Owner" (prefix table owner) check box in the
Advanced Options pane. A known limitation with the feature
requires that you select the check box in the Advanced
Options pane before you work with the Left or Right Object
Selection tree. If you do not select the advanced option
first, the object selection tree is not refreshed.
All published fixes for this product can be found through
Published Solutions on CA Support Online.
The PDF guides for this product are as follows:
- AllFusion ERwin Data Modeler Implementation Guide
(ERwin_Impl.PDF)
- AllFusion ERwin Data Modeler Methods Guide (ERMethods.PDF)
- AllFusion ERwin Data Modeler Release Summary
(ERwin_RelSum.PDF)
- AllFusion ERwin Data Modeler API Reference Guide
(ERwin_API_Ref.PDF)
- CA ERwin Data Modeler and Microsoft Visual Studio Team
System 2008 Database Edition Integration Guide
(ERwin_VSDB_Int.PDF)
To view PDF files, you must download and install the Adobe
Reader from the Adobe website if it is not already
installed on your computer.
The release number on the title page of a document might
not correspond to the current product release number;
however, all documentation delivered with the product,
regardless of release number on the title page, will
support your use of the current product release. The
release number changes only when a significant portion of a
document changes to support a new or updated product
release. If no substantive changes are made to a document,
the release number does not change. For example, a document
for r7 may still be valid for r7.1 or even r7.2.
Documentation bookshelves always reflect the current
product release number.
Occasionally, we must update documentation outside of a new
or updated release. To indicate a minor change to the
documentation that does not invalidate it for any releases
that it supports, we update the edition number on the cover
page. First editions do not have an edition number.
Contact Technical Support
For online technical assistance and a complete list of
locations, primary service hours, and telephone numbers,
contact Technical Support at http://ca.com/support.
Provide Feedback
If you have comments or questions about CA product
documentation, you can send a message to techpubs@ca.com.
If you would like to provide feedback about CA product
documentation, please complete our short customer survey,
which is also available on the CA Support website.
Copyright © 2008 CA.
All rights reserved.