Release Notes

From ER/Studio Data Architect
Jump to: navigation, search

Welcome to ER/Studio Data Architect 2016

ER/Studio Home | ER/Studio Documentation | Technical Support |

Read Me Last Updated: May 27th, 2016.

DBTA_Award.jpg TrendAward.png Award.png CS-Award-Top-25-Publisher-2012-13-Medium.gif RC04.gif bestshowreadme.gif pcweekchoice0628.gif pcmaguk.gif dmreview1999.gif logo_sqlfrontrunner.gif SD2014.png

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.

Release Notes

Important Installation Notes
Important Release Advisory
Bug Fixes

Upgrade Instructions

Upgrading from IDERA Connect to ER/Studio Team Server
Upgrades for ER/Studio Repository users
Upgrades for version of ER/Studio Repository prior to 2016

Release 2016 features summary:

Release Notes

Important Installation Notes

  • If you are going to install the x64 bit client version of ER/Studio Data Architect you must uninstall any previously installed x32 bit versions of the software.
  • To install ER/Studio Data Architect on Microsoft Windows, 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:
      • C:\ProgramData\IDERA\ERStudioDA_X.X\DatatypeMapping
    • For Automation Handler files, which is also the default location for sample macros:
      • 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:
      • 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:
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\RepoIn
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\RepoOut
    • Default directory for Report files:
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\Report
    • Default directory for SQL scripts:
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\SQLCode
    • Default directory for Quicklaunch files:
      • C:\Users\<user>\AppData\Roaming\IDERA\ERStudio\XML
    • Default Save location for new diagrams:
      • C:\Users\<user>\Documents\ERStudioDA_X.X

Important Release Advisory

  • Note regarding installing on Windows 10.

In some situations, background tasks may cause the installation to appear as though it has stopped, even though the progress on the setup window is indicating 100%. In these instances there may be a popup message indicating that a restart is required to finish installation. However, that message may be hidden behind the setup window. Try pressing ALT + TAB to bring the message to the foreground and answer to restart your computer and finish the installation.

  • To ensure compatibility with ER/Studio Repository synchronization, this version of ER/Studio Data Architect requires at least ER/Studio Repository version 2016 for all Repository operations.

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

  • License Enforcement.

When working with the Repository, all users must use the same license type. ER/Studio now enforces this by marking the Repository as an Enterprise Team Edition Repository when a user with an Enterprise Team Edition license logs in. Subsequent log in attempts by users with a non-Team Edition license will not be allowed

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 16.0.3

ERS-25756 Domain-based attributes in model published in Team Server display wrong datatype.
ERS-25762 Parentheses in DDL not correct for default values.

Bugs Fixed in ER/Studio Data Architect 16.0.2

ERS-25198 Iteration over index columns shows very slow performance.
ERS-25405 Case sensitivity issue renders the 'Hide other users' feature ineffective.
ERS-25532 Reverse Engineer from SQL Server 2014 does not get the default values for columns
ERS-25589 Opening a data model crashes the application.
ERS-25603 ERDA crashes after adding attribute to entity on a submodel.

Known Issues Fixed in ER/Studio Data Architect 16.0.2

ERS-25024 Teradata JSON datatype is not imported from a SQL file
ERS-25134 ContainedObject count method always returns 0 for Business Data Objects

Bugs Fixed in ER/Studio Data Architect 2016 (16.0.0)

ERS-24626 Roll up of one subtype among many causes FK to be removed from other subtypes.
ERS-24959 "MIRSETUP.XML" is missing from "\MetaIntegration\conf" folder.
ERS-22486 Default the Place New Objects Near Existing Objects parameter in the Submodel Editor to checked.
ERS-24407 Submodel Editor - include option to hide existing submodels from editor.
ERS-24893 For Enterprise XE7 license, comment edit box is not shown on "Repository Check In" window.
ERS-24917 Length of NVARCHAR, VARCHAR and VARBINARY is displayed as 0 instead of max.
ERS-24931 Copy and paste of entity with varchar(max) or nvarchar(max) does not preserve the data type setting.
ERS-24496 Teradata - Date format default value generates incorrect Syntax.
ERS-24620 Reverse engineering Teradata column lengths are incorrect.
ERS-24609 Teradata decimal columns are being erroneously reverse engineered from database into model as IDENTITY columns.
ERS-24724 TERADATA - Reverse engineering CLOB columns results in defined lengths being incorrect.
ERS-18123 Ability to generate column comments for MySQL.
ERS-24770 Undo causes instability in Data Architect after check out from Repo.
ERS-24482 VARCHAR(MAX) is being generated as VARCHAR(4000) for MS SQL Server 2014.
ERS-16232 Ability to remove double quotes from table and column names.
ERS-23897 When running a roll-up denormalization a relationship is deleted.
ERS-24284 Dropping relationship on roll-up denormalization.
ERS-24801 Inconsistent formatting results.
ERS-24743 Data Diagram Version Upgrade causes instability on a database upgrade from v6.0 to v7.0.
ERS-23629 Templated procedures now included when using GenDLLUsingFileBasedQuickLaunch.
ERS-24661 Korean language order is showing incorrectly.
ERS-24602 The documentation incorrectly lists that Trigger.Text is a read-write property.
ERS-24745 XML Schema Generation, Entity Option, "Add element refs to parent entity elements" is not adding reference to parent complex type.
ERS-24322 Data Architect becomes unstable when getting a particular model due to incorrect positions of shapes.
ERS-24633 Option to compare schemas is missing.
ERS-24681 Reverse engineering Teradata. Error: ‘The parameter is incorrect’.
ERS-24714 Error when setting a named release.
ERS-24062 Term hyperlinks are not shown with Firefox when first clicked.
ERS-24419 Users must close and reopen the Entity Editor after applying a Naming Standards Template.

Known Issues

ERS-24515 Unable to reverse engineer Teradata database with collect statistics enabled
ERS-24577 Change record marked as completed even if the check in fails in the server
ERS-24773 Parse error on import due to use of certain keywords in Oracle sql file.
ERS-24926 Editors no longer wrap text for definition, notes
ERS-24996 Objects included in Business Architect subject areas not shown in Universal Mappings Editor
ERS-25004 "Team Server Data Source" option unavailable in Reverse-Engineer after log in
ERS-25024 Teradata JSON datatype is not imported from a SQL file
ERS-25134 ContainedObject count method always returns 0 for Business Data Objects
ERS-25155 Entities remain above Business Data Objects in diagram view after being removed
ERS-25166 Instability when generating reports on Japanese system with Welcome Page open
ERS-25285 TS: With SSL Enabled, Get Diagram errors: Socket Disconnected Error
ERS-25358 Errors refreshing tree nodes when working with Business Data Objects
ERS-25359 Teradata temporal types not fully supported in SQL import
ERS-25360 Teradata temporal types not fully supported in Alter SQL generation

Upgrade Instructions

Upgrading from IDERA Connect to ER/Studio Team Server

For detailed instructions on upgrading to ER/Studio Team Server, see Team Server Upgrade Notes.

Upgrades for ER/Studio Repository users

See Upgrading From Previous Versions.

To ensure compatibility with ER/Studio Repository synchronization, this version of ER/Studio Data Architect requires at least ER/Studio Repository version 2016 (Now included on Team Server installer)for all Repository operations. To use this version of ER/Studio Data Architect, you will need to upgrade your Repository version to at least version 2016. Please note, backward compatibility is not posible.

IDERA Technical Support

To contact Support, go to Customer Support Center.

See Also