Welcome to ER/Studio Data Architect® 16.5 (2016+)

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


Thank you for using IDERA 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 DA'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.

See the most recent documentation at the IDERA Web site, https://www.idera.com/support/productdocuments


WHAT'S NEW in version 16.5

Universal mappings enhancements

Improved relationship diagramming

Improved glossary integration

Added database support

Expanded change management features

IDERA Rebranding

Supports rich text functionality on entry fields

Added the ability to inherit relationship color from parent entity

Implemented unique tokens to identify repository checkout records

Improved repository security for new users and assigned roles

what’s new in version 2016

Business Data Objects
Model/Submodel NSTs
Windows 10 Support
Teradata Support
Teradata Enhancements
SQL Azure Support

Release Notes

Important Installation Notes

Important Release Advisory

Bug Fixes

Known Issues

Upgrade Instructions

Upgrading from ER/Studio Portal to Team Server

Upgrades for version of ER/Studio Repository prior to 2016

Additional Resources

Licensing Your IDERA Product

IDERA Product Support

IDERA Technical Support

IDERA on the Web

What's New in Version 16.5

Universal mappings enhancements

ER/Studio Enterprise Team Edition 16.5 expands universal mapping to include mappings between entity/table and attribute/column across design layers. Users now can add and view definitions, attachments, and notes related to Universal Mappings. For more information about universal mappings, see Working with Universal Mappings.

Improved relationship diagramming

Viewing data models can occasionally become cluttered with the number of relationships associated with the model. The Data Model View in ER/Studio Data Architect 16.5 introduces a toggle option that allows you to hide or unhide one, more, or all relationships in a submodel. To hide a relationship, simply select and right-click the item(s) you want to hide or unhide, and then select either Hide Relationship or Show All Hidden Relationships from the available menu. Note that when publishing models to Team Server, all hidden relationships remain hidden in the graphical display. For more information about managing relationships, see Creating and Editing Relationships.

Improved glossary integration

ER/Studio Data Architect XE7 introduced the ability to automatically link your Team Server glossaries directly into the ER/Studio interface. ER/Studio Enterprise Team Edition 16.5 continues to improve this feature by allowing association of specific models or sub-models in a .dm1 file and repository to be associated with a specific glossary. That glossary then can provide the scope when trying to detect and link terms to the model objects. If a glossary term is used in the Name, Definition, or Notes of a model object, it is highlighted to identify that you have a definition in your Team Server Glossary. Holding your mouse cursor over the highlighted term pops up the short definition while control-clicking on the term will navigate to that term in the Team Server Glossary. For more information about glossaries, see Glossary Integration or the ER/Studio Team Server online help section about Working with Glossaries.

Added database support

ER/Studio Data Architect 16.5 now includes database platform support for IBM DB2 for z/OS v11.x and SQL Server 2016 (does not include support for SQL Server 2016 JSON capabilities). For more information about supported platforms, see Supported Database Platforms.

Expanded change management features

ER/Studio Enterprise Team edition includes additional features to expand the support for Agile change management. Users now can associate tasks from third-party tools, such as Atlassian JIRA, to specific projects available within the Repository Project Center. Similar support also is expanded in Team Server, where you can add, change, and delete the same tasks. JIRA is the only issue- and project-tracking tool supported in this release. For more information about using this feature, see Change Records and Working with Repository Projects.

IDERA Rebranding

This release begins a rollout of rebranding this product from Embarcadero to IDERA. Note that these changes include a new license agreement, installation and data directories, icons, file names, registry settings, and more. For more information about IDERA and IDERA products, see www.idera.com.

Supports rich text functionality on entry fields

All fields where a user can type names, definitions, notes, etc. now include a spell check, allow some rich text functions such as bold and underlined text, and support embedded hyperlinks. In larger fields, a text wrap feature also was implemented. Available rich text options include:

·         Text font, color, and size

·         Bold, italics, and underline

·         Format and alignment options including bullets

·         Hyperlink capability

Added the ability to inherit relationship color from parent entity

The Colors & Fonts dialog now includes the Inherit from parent entity foreground checkbox that allows users to set whether you want the outline of an entity to be the same color as its parent entities. If you select a relationship and change its color, the manual change overrides the color inherited from the parent. Changes made in a child entity do not affect the color of the parent. For more information about setting diagrams colors, see Setting Default Diagram Colors and Fonts. This option is enabled only for the following object types when selected from the drop-down list available in the Colors & Fonts dialog:

·         Relationship object type. Relationship color is the same as the parent entity foreground (border.)

·         Inherited Primary Keys object type. Primary font color is the same as parent entity foreground (border).

·         Inherited Non-Keys. Foreign key color is the same as parent entity foreground (border).

Implemented unique tokens to identify repository checkout records

In this release of ER/Studio Data Architect, checkouts now include a unique identifier or token to easily resolve identification issues when attempting to check in to the Repository. Previously, checkouts included the host machine name as part of the identifier in the checkout record. This process caused issues in virtualized environments when the host names did not match upon reconciliation at check in, perhaps because the user disconnected from the repository before checking in the work.

Improved repository security for new users and assigned roles

This release of ER/Studio Repository features the following security enhancements to the Security Center:

·         When a new user is added, the user has the ability to log into the repository but has NO ACCESS to projects. An administrator must assign a role with the proper access to this user account.

·         Role assignment is inherited by all objects under the node for which the role is specified. For example, if you grant UserA access ProjectX, then UserA can access all elements under ProjectX. But if you want to restrict UserA's access to only a single element within ProjectX, such as Model1, you can grant access to Model1 while also granting a NO ACCESS role to UserA at the ProjectX level. The lower level access to Model1 has a higher priority than the ProjectX NO ACCESS role.

For more information about managing repository security, see Establishing Security for the Repository.

What's New in Version 2016

Business Data Objects

Model/Submodel NSTs

You can now bind Naming Standards Templates to Models and Submodels

Windows 10 Support

You can now install your favorite Data Modeling software on your newest OS.

Teradata Support
We now support Teradata 15.x.

Teradata Enhancements

AS VALIDTIME.
AS TRANSACTIONTIME.

 

SQL Azure Support
Microsoft SQL Azure is now fully supported for all operations.

Release Notes

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

Important Installation Notes


Important Release Advisory


Bug Fixes


Bugs Fixed in ER/Studio BA 16.5

Bug #

Description

ERS-22178

Column names of foreign keys in physical models are now editable when no rolename specified

ERS-24199

Increase the length of the Attribute Name and Column Name display fields

ERS-24644

Macros do not work and next error pops up when closing application: WinWrap Basic control isn’t registered properly on your computer

ERS-24926

Editors no longer wrap text for definition, notes

ERS-24927

View warning when modifying the primary key

ERS-25826

Deleting object in BDO causes corruption, Repository errors

Bugs Fixed in ER/Studio DA 16.0.3

Bug #

Description

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 DA 16.0.2

Bug #

Description

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 submode.

Bugs Fixed in ER/Studio DA 2016

Bug #

Description

ERS-24626

Roll up of one subtype among many causes FK to be removed from other subtypes.

ERS-22959

"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 option to hide existing submodels from editor.

ERS-24893

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


Known Issues Fixed in ER/Studio DA 16.5

Bug #

Description

ERS-24515

Teradata databases with collect statistics enabled cannot be reverse-engineered.

ERS-24577

Change Records are marked as completed even if the check in fails in the Repository server.

ERS-24773

Certain keywords cause parser errors when importing an Oracle SQL script.

ERS-24926

Definitions and Notes are no longer wrapped in editors.

ERS-24996

Objects included in Business Architect subject areas are not shown in Universal Mappings Editor.

ERS-25004

The Team Server Data Source option is unavailable in the Reverse-Engineer Wizard after log in.

ERS-25024

The Teradata JSON datatype is not imported from a SQL file.

ERS-25134

The ContainedObject count automation method always returns 0 for Business Data Objects.

ERS-25155

Entities remain above Business Data Objects in the diagram view after being removed.

ERS-25166

Crashes may occur when generating reports on Japanese system with Welcome Page open.

ERS-25285

Using the SSL option for the Repository may cause a "Socket Disconnected" error.

ERS-25358

Errors may occur while refreshing tree nodes when working with Business Data Objects.

ERS-25359

Teradata temporal types are not fully supported in SQL Import.

ERS-25360

Teradata temporal types are not fully supported in Alter SQL generation.

ERS-26106

Column definition field disappears when resizing editor

ERS-26109

Note override checkbox cannot be clicked by mouse

Known Issues Fixed in ER/Studio DA 16.0.2

Bug #

Description

ERS-25024

Teradata JSON datatype is not imported from a SQL file.

ERS-25134

ContainedObject count method always returns 0 for Business Data Objects.

Upgrade Instructions

Upgrading from ER/Studio Portal to ER/Studio Team Server


For detailed instructions on upgrading to Team Server, see the Upgrade Notes.

Upgrades for ER/Studio Repository users


To use the repository with this release, you will need to be running at least version 2016 of Repository as a minimum.

Upgrades for version 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 the latest upgrade notes online.

Additional Resources

Licensing Your IDERA Product

All IDERA products include a 14-day trial period. To continue using the product without interruption, we recommend that you license it as soon as possible. For information on licensing your product, refer to the Quick Start Guide. If you have not yet purchased this product, contact sales@idera.com.

IDERA Product Support

The IDERA Web site is an excellent source for additional product information, including white papers, articles, discussion forums, and the IDERA Knowledge Base. Visit www.idera.com/support, or click any of the links below, to find:

IDERA Technical Support

If you have a valid maintenance contract with IDERA, the Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of IDERA products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation (14 days).

We encourage you to open technical support cases via the Customer Support Center. For additional information about IDERA Technical Support, visit the Support section of our Web site.

IDERA on the Web

To download evaluations of other IDERA products or to learn more about our company and our products visit us at www.idera.com.