Release Notes 9.6.1

Welcome to ER/Studio Data Architect 9.6.1

ER/Studio Home | ER/Studio Documentation | IDERA Technical Support | IDERA.com

Read Me Last Updated: Oct. 23, 2013.

---

Thank you for using ER/Studio Data Architect, previously known as ER/Studio, the award-winning data modeling application for logical and physical database design and construction. ER/Studio Data Architect's (ER/Studio DA) powerful, multi-level design environment addresses the everyday needs of database administrators, developers and data architects who build and maintain large, complex database applications.

ER/Studio Data Architect's progressive interface and processes have been logically organized to effectively address the ease-of-use issues that have plagued data modeling tools for the past decade. The application facilitates your ability to create, understand and manage the mission-critical database designs within an enterprise. It offers strong logical design capabilities, bidirectional synchronization of logical and physical designs, automatic database construction, accurate reverse engineering of databases, and powerful HTML-based documentation and reporting facilities. Before you use ER/Studio, please read the information below.

WHAT'S NEW in 9.6.1

New DBMS Platform Support - Firebird
Increased Memory Availability

WHAT'S NEW in 9.6

IDERA Connect
New Platform Version Support
New InterBase Object Types
SQL Server Sequences
Oracle Named NOT NULL Constraints

Release Notes

Important Installation Notes
Important Release Advisory
Known Issues
Bug Fixes

Upgrade Instructions

Upgrading from ER/Studio Portal to IDERA Connect
Upgrades for ER/Studio Repository 6.5 users
Upgrades for version of ER/Studio Repository prior to 6

WHAT'S NEW in 9.6.1

New DBMS Platform Support - Firebird

Firebird 2.x: Officially supports Firebird 2.1 and 2.5.

Firebird 1.5: Officially supports Firebird 1.5.

Increased Memory Availability

ER Studio DA is now able to use up to 4GB of memory on 64 bit machines and up to 3GB of memory on 32 bit Windows..

WHAT'S NEW in 9.6

IDERA Connect

Connect is a new IDERA product. For ER/Studio Data Architect, Connect provides the following:

• It replaces functionality previously provided by ER/Studio Portal
• Data source definitions stored on a Connect server can be used in data source-centric ER/Studio Data Architect functions such as reverse engineering, DDL generation, and Compare/Merge.

New Platform Version Support

As of this release, ER/Studio Data Architect functionality is available against the following platform versions:

• TeraData 14
• IBM DB2 for Linux, Unix, and Windows Version 10
• Netezza 7
• InterBase XE
• InterBase XE3

New InterBase Object Types

Against InterBase 2009, XE, and XE3 datasources, object types generators, triggers, and procedures are now supported.

SQL Server Sequences

Sequences, introduced in SQL Server 2012, are now supported by ER/Studio Data Architect.

Oracle Named NOT NULL Constraints

ER/Studio Data Architect now provides dedicated support for Oracle's named NOT NULL constraints.

Release Notes

Important Installation Notes

• To install ER/Studio Data Architect on Windows 8, Windows 7, Windows Vista, Windows XP Professional, or Windows XP Home Edition, you must have administrative privileges. Once you have installed ER/Studio Data Architect, you can then log in as a standard or limited user and use the application without having administrative privileges.
• In order to run ER/Studio Data Architect, you must provide valid licensing information.
• When you install ER/Studio Data Architect, certain files and directories that were previously stored under the Program Files folder are now by default installed to system-specified application data directories.
• During installation, the following directories are created:
  • For Datatype Mapping Editor files, which is also the default location for user-generated Datatype Mapping files:
    • Windows XP: C:\Documents and Settings\All Users\Application Data\IDERA\ERStudioDA_X.X\DatatypeMapping
    • Windows 8, Windows 7, and Windows Vista: C:\ProgramData\IDERA\ERStudioDA_X.X\DatatypeMapping
  • For Automation Handler files, which is also the default location for sample macros:
    • Windows XP: C:\Documents and Settings\All Users\Application Data\IDERA\ERStudioDA_X.X\Macros
    • Windows 8, Windows 7, and Windows Vista: C:\ProgramData\IDERA\ERStudioDA_X.X\Macros
  • For sample model files, for which a shortcut is generated in the ER/Studio Data Architect program group:
    • Windows XP: C:\Documents and Settings\All Users\Application Data\IDERA\ERStudioDA_X.X\Sample Models
    • Windows 8, Windows 7, and Windows Vista: C:\ProgramData\IDERA\ERStudioDA_X.X\Sample Models
• When the application is run for the first time, the following directories are created by ER/Studio Data Architect:
  • Directories used by the Repository client to transfer files to and from the Repository server:
    • Windows XP:
      • C:\Documents and Settings\<user>\Application Data\IDERA\ERStudio\RepoIn
      • C:\Documents and Settings\<user>\Application Data\IDERA\ERStudio\RepoOut
    • Windows 8, Windows 7, and Windows Vista:
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\RepoIn
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\RepoOut
  • Default directory for Report files:
    • Windows XP: C:\Documents and Settings\<user>\Application Data\IDERA\ERStudio\Reports
    • Windows 8, Windows 7, and Windows Vista: C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\Report
  • Default directory for SQL scripts:
    • Windows XP: C:\Documents and Settings\<user>\Application Data\IDERA\ERStudio\SQLCode
    • Windows 8, Windows 7, and Windows Vista: C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\SQLCode
  • Default directory for Quicklaunch files:
    • Windows XP: C:\Documents and Settings\<user>\Application Data\IDERA\ERStudio\XML
    • Windows 8, Windows 7, and Windows Vista: C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\XML
  • Default Save location for new diagrams:
    • Windows XP: C:\Documents and Settings\All Users\Application Data\IDERA\ERStudioDA_X.X\Sample Models
    • Windows 8, Windows 7, and Windows Vista: C:\Users\<user>\Documents\ERStudioDA_X.X

Important Release Advisory

ER/Studio Portal is no longer supported by ER/Studio Data Architect. Most functionality formerly provided by ER/Studio Portal is now provided by IDERA Connect. Users that formerly used the Repository tab to browse the portal can use a Web browser instead.

Known Issues

ERS-21891	Partial layout should only affect the edges between the selected nodes.
ERS-22022	Universal Mappings for objects in the same file don't show up in Reports.
ERS-22037	Universal Mappings between objects in the same file aren't displayed properly in the Where Used.
ERS-22202	Generated by default option does not work correctly in logical to physical compare.
ERS-22206	Unmatching objects in the Compare Wizard does not automatically delete mappings between the objects.
ERS-22230	Problems with Universal Mappings in the View Editor Where Used tab.
ERS-22720	Cannot copy/past database objects between different versions of InterBase.
ERS-22775	SQL parse problem when trying to copy/paste a SQL Server sequence.
ERS-22818	Partitions are reverse engineered as separate tables on Greenplum.

Bug Fixes

Use your browser Find feature to locate a particular bug number or click a link below to see the issues addressed in a specific build.

== Bugs Fixed in ER/Studio Data Architect 9.6.1 ==

ERS-22143	Rolenames are now cleaned up when a child table is copied and pasted without it's parent table.
ERS-22388	Netezza index columns are now reverse-engineered in the proper order.
ERS-22680	The automation interface now properly adds attachments to Oracle sequences and materialized views.
ERS-22329	The Dictionary object in the automation interface now has the ID property exposed.
ERS-22730	The Datatype Mapping editor now supports single-quotes, double-quotes, commas, and periods.
ERS-22818	Greenplum partitions are not reverse-engineered properly.
ERS-22903	Attachment values are now exported properly to ERWin when using the MetaWizard.

== Bugs Fixed in ER/Studio Data Architect 9.6 ==

ERS-19031	The tab order is now correct in the Phrases tab of the Relationship editor.
ERS-20895	Defaults bound to domains are now maintained when generating physical models.
ERS-21174	The Repository will no longer allow cross-dictionary bindings.
ERS-21271	A diagram with a missing default name property will no longer cause the Repository to crash.
ERS-21609	The Repository has been certified to run using SSL 3.0.
ERS-22334	SQL Server sql import now properly imports nvarchar(max) columns.
ERS-22395	The Repository now properly maintains dictionary bindings between main and branched diagrams.
ERS-22492	HTML Report performance has been improved when the Attribute Where Used option is selected.
ERS-22522	The application now remains stable when the Help button is clicked in the Denormalization Mapping wizard.
ERS-22534	The Repository now remains stable and returns an error when an operation requires more than the available memory.
ERS-22535	The Repository services now use a quoted path upon installation.
ERS-22587	Long stored procedure text is no longer truncated in the Compare Wizard.
ERS-22659	The Repository Branch/Merge feature now properly handles attachment text lists
ERS-22666	Custom physical datatype mappings are now preserved when exporting through the MetaWizard to an ERWin physical-only model
ERS-22667	z/OS v10 physical models can now be reverse-engineered.
ERS-22668	The Repository now properly handles diagrams with Universal Mappings.
ERS-22686	It is now possible to edit a table that contains both single and multi-byte characters (Japanese version only)
ERS-22697	The line numbering in the Constraints tab of the Table Editor has been fixed.
ERS-22740	VARCHAR datatype widths are now reverse-engineered properly from Paradox databases.
ERS-22753	ER/Studio now supports z/OS v10 triggers and views.

Upgrade Instructions

Upgrading from ER/Studio Portal to IDERA Connect

For detailed instructions on upgrading to Connect, see Connect Upgrade Notes.

Upgrades for ER/Studio Repository 6.5 users

Keep the following in mind when updating for this release:

• Only a service upgrade is required
• No diagram data version upgrade is required.
• There are no database changes from version 6.5

Upgrades for version of ER/Studio Repository prior to 6

Use the following checklist to ensure ER/Studio Repository is correctly upgraded.

Upgrade Checklist

• Download ER/Studio Enterprise Upgrade. To download the most current release, go to embarcadero.com.
• Review the ER/Studio ReadMe. For the most current installation and usage information, see the ReadMe at docs.embarcadero.com.
• Prepare to upgrade. For what to do before you upgrade to the latest version, see Preparing to Upgrade.
• Upgrade ER/Studio Repository. For ER/Studio Enterprise installations, which include the Repository. For ER/Studio Repository upgrade details, see Upgrading the Repository.

Important Notes

• The Repository upgrade must be done incrementally from one major version to the next until the target version is reached. You cannot skip major versions during the Repository upgrade as the installer for each major version only contains the database changes between the new version and the previous one. When upgrading from earlier versions, such as from 5.5 to Repository 6.5, you must first upgrade the Repository to version 6.0, update the database, uninstall version 6.0, then upgrade to 6.5, and update the database. Once the Repository upgrade is complete and you have installed the latest version of ER/Studio Data Architect, then you should upgrade your diagrams with the latest version of ER/Studio Data Architect. For more information, see the online documentation. Consult IDERA Technical Support when upgrading from versions prior to 4.5.
• If you are upgrading to ER/Studio Repository, upgrade your version of ER/Studio Data Architect also. Ensure the build date of ER/Studio Repository coincides with the build date of ER/Studio Data Architect.
• If you are also using ER/Studio Portal, you must also upgrade it to the latest version.
• You can install ER/Studio Data Architect 9.x and an earlier ER/Studio Data Architect version on the same workstation.
• Any *.dm1 files you use from the previous version will be copied and converted to 8.x format when you open them for the first time. You can then save the diagram with a different name or use the same name to write over the old file. Previous versions of ER/Studio Data Architect will not read 8.x and higher files.
• Upgrading diagrams can be time consuming and memory intensive. The number and size of ER/Studio Data Architect diagrams managed in the upgraded Repository dictates how long the upgrade process takes.
• Reference Models, supported in previous versions, are not supported in ER/Studio Data Architect 7.x and later versions.

Preparing to Upgrade the Repository

1. Ensure you have backed up all your.dm1 files.
2. Check in all your diagrams and objects.

   Note: If you try to check in a file from the previous version with the same name as a current file, the current file will become corrupted.

3. Rename all local copies of Repository diagrams in the active file directory as follows:

   • Choose Repository > Options.

     Make note of the Active File Directory.

     Switch to the Windows Explorer and rename all the diagrams in the Active File Directory.

4. Ensure no one is logged into the Repository.
5. Backup the current Repository database.
6. Restart the Repository host computer.

Upgrading the Repository

Note: This procedure is for ER/Studio Enterprise installations only, which include the Repository. When you upgrade ER/Studio Data Architect you must also upgrade ER/Studio Repository to correspond with the same build date as ER/Studio Data Architect.

1. Log on to Windows with local administrator privileges.
2. Start the Repository installation program and select Repair Repository Services. The installation program starts the following services:

The Repository services and your existing database will be upgraded to the current version.

Note: If you are upgrading from a Repository version prior to 4.0, you can delete the C:\Program Files\IDERA\Repository\Data directory . This directory is not used with Repository versions 4.0 and later.

IDERA Technical Support

To contact Support, go to embarcadero.com/support.

Comments: Email Us