Release Notes

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

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.

Important Installation Notes

  • To install ER/Studio Data Architect on Windows 10, 8.1, 8, or 7, you must have administrative privileges. Once you have installed ER/Studio DA, 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 DA, you must provide valid licensing information.
  • When you install ER/Studio DA, 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:
    • For Automation Handler files, which is also the default location for sample macros:
    • For sample model files, for which a shortcut is generated in the ER/Studio DA program group:
      C:\ProgramData\IDERA\ERStudioDA_XXXX\Sample Models
  • When the application is run for the first time, the following directories are created by ER/Studio DA:
    • Directories used by the Repository client to transfer files to and from the Repository server:
    • Default directory for Report files:
    • Default directory for SQL scripts:
    • Default directory for Quicklaunch files:
    • Default Save location for new diagrams:
      C:ProgramData\IDERA\ERStudioDA_XXXX\Sample Models

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.

Ensure Repository Sync

To ensure compatibility with ER/Studio Repository synchronization, this version of ER/Studio Data Architect requires ER/Studio Repository version 17.0 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 who 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 are not allowed.

Bug Fixes and Known Issues

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 17.0.2

ERS-25070 Corrected a problem in which the scroll bar on the model tree explorer would disappear when adding a large number of Business Data Objects to a model.

This means users had to press page-up/page-down to move up or down the tree in large models.

ERS-26103 When changing one table, multiple tables would sometimes appear in the "Review Changes" dialog when checking in to the repository.
ERS-26216 Users set to "No Access" authorization at the Project level could see models under that they were not authorized to for that project.
ERS-26237 When editing Business Data Object names on the diagram surface (not within the editor), the entry of a duplicate BDO name was causing the application to halt.
ERS-26273 When moving a submodel to be a child of another submodel, Business Data Objects that were in that submodel did not get moved.

All other objects moved correctly, and were still bound to their respective BDO's, but the BDO frames did not appear in the submodel.

ERS-26297 Resolved intermittent conflicts on repository check-in for DB2 tablespaces.
ERS-26411 Intermittent errors were being triggered when performing "Get Latest" from the repository for diagrams that had relationships that inherited color defaults from their parent entity specified.
ERS-26410 DL import from MetaWizard now creates Data Flows without "-ppus" Miscellaneous parameter.
ERS-26479 Intermittent error when importing flat files using the Metawizard bridge.
ERS-26506 A regression bug was introduced in the 17.0 release which could prevent the ability to create a model branch in the repository.

This is corrected and branch and merge functionality is now executing properly.

Bugs Fixed in ER/Studio Data Architect 17.0.1

ERS-26333 ER/Studio viewer icon was replaced.
ERS-26361 License terms link has been corrected to point to the correct license agreement.

Bugs Fixed in ER/Studio Data Architect 17.0

ERS-25742 When reverse engineering Hive, some datatypes are not coming through correctly and are reverting to the default datatype specified in physical options.
ERS-25760 CheckIn/CheckOut comments longer than 255 characters are not saved correctly.
ERS-25991 Sample models shipped with the product are updated with IDERA naming.
ERS-25993 Under some conditions, the application hangs when generating a physical model.
ERS-26018 Corrections to spell check are not working in some situations due to embedded formatting.
ERS-26022 Corrected filter to exclude projects with JIRA association from the Unassociated Tasks list.
ERS-26025 Descriptions for tasks associated with a JIRA project should not be editable within ER/Studio Data Architect. Edits are synchronized from JIRA.
ERS-26031 This release includes MetaWizard Import/Export Bridges version 9.1.
ERS-26033 Incorrect message appears when opening a DM1 file that was created from a previous version of ER/Studio Business Architect conceptual model.
ERS-26055 Correction to "Has details" indicator when checking in universal mappings.
ERS-26061 When reverse engineering Hive, some datatypes are not coming through correctly and are reverting to the default datatype specified in physical options.
ERS-26087 User should get a confirmation dialog to edit JIRA tasks associated with a project if he is not logged in to Team Server.
ERS-26093 Business glossary terms that contain special characters, such as parentheses, are not getting highlighted correctly in editors to show associated link to the glossary.
ERS-26146 Updated the application launch splash screen.
ERS-26172 The newest version of the MetaWizard Import/Export Bridges (9.1.0) is included in this release. There are several new bridges and improvements to existing bridges, including:
  • Amazon S3 (Simple Storage Service) import (beta bridge)
  • Apache Hadoop Distributed File System (HDFS Java API) import or (WebHDFS REST API) import (beta bridge)
  • Posix (Windows/Linux) File System import (beta bridge)
  • Flat File Database (CSV or Excel) import (beta bridge)
  • JSON (JavaScript Object Notation) Database Files import
  • Apache Avro Database Files (JSON) import
  • Apache Parquet Database Files import
  • Apache Hadoop Hive Database (HCatalog via JDBC) import
  • Apache Hadoop Hive Database (Web Hcatalog) import
  • Apache Hadoop Hive Database (Hive Metastore via JDBC) import (beta bridge)
  • MongoDB Database (JSON) import (improved)
  • Apache CouchDb Database (JSON) import
  • MarkLogic NoSQL Database (for JSON only) import
  • Apache Cassandra Database import (improved)
  • DataStax Enterprise (Cassandra) import
  • Actian Vector (Vectorwise) Database Database (via JDBC) import
  • HP Vertica Database (via JDBC) import
  • Oracle MySQL Database (via JDBC) import

Major SQL parsing improvements for lineage:

  • Microsoft SQL Server Database (via JDBC) import
  • Oracle Database (via JDBC) import
  • Pivotal GreenPlum Database (via JDBC) import
  • PostgreSQL Database (via JDBC) import
  • Teradata Database (via JDBC) import
  • SQL Scripts (major SQL parsing improvements for lineage)
  • Apache (Cloudera, Hortonworks, MapR) Hadoop HiveQL Script import
  • IBM DB2 Universal Database (UDB) SQL Script import (beta bridge)
  • Oracle Database SQL Script (PL/SQL) import
  • Teradata Database SQL Script (BTEQ) import

SQL DDL import major improvements:

  • Apache (Cloudera, Hortonworks, MapR) Hadoop HiveQL DDL import
  • Oracle Database DDL import
  • Teradata Database SQL DDL import
ERS-26191 Within data lineage, opening tables or attributes under other sources was causing the application to hang.
ERS-26226 Within data lineage, creating tables under other sources was causing the application to hang.
ERS-26233 In data lineage, when opening attribute details under transformations or output details, the application would hang if tables from "other" sources were included.
ERS-26240 In some situations, adding a diagram to the repository was causing a unique index violation.
ERS-26277 Corrected a bug that could cause ER/Studio Data Architect to hang when deleting a task in the Change Management Center.
ERS-26281 Corrected a bug when linking change records to tasks that originated from JIRA.

Known Issues

ERS-26344 Repository service stops when attempting invalid LDAP login
ERS-26256 Unable to save Data Model after adding Data Movement Properties and Data Lineage
ERS-25535 SQL Generation cuts off default values

Upgrade Instructions

Upgrading from ER/Studio Portal 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

To use the repository with this release, you must run ER/Studio Repository 17.0.

Upgrades for versions of ER/Studio Repository prior to 2016

Repository is now installed as part of Team Server. To upgrade an earlier version of Repository, please see Upgrading From Previous Versions.

IDERA Technical Support

To contact Support, go to Customer Support Center.

See Also