What's New

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

Go Up to Getting Started with ER/Studio Data Architect

You can find information on previous versions in the side bar.

The following feature summary areas are available in this topic:

20.1 ER/Studio Data Architect Features Summary

Adds support for Index column ordering in PostgreSQL 10.x-12.x

ER/Studio Data Architect 20.1 includes support for Index column ordering in PostgreSQL 10.x to 12.x. You now can define the Sort Order for the columns. Available options are ASC for ascending order and DESC for descending order.

ERDA 201 Index Column Ordering.jpg

Allows user-defined names for the History Table in Azure SQL DB and SQL Server

For ER/Studio Data Architect Azure SQL DB and SQL Server users, the History Table name now is customizable. You can enter any name as long as it is not already existing in the database.

ERDA 201 History Table.jpg

Allows a user to select a region when reverse engineering in Google BigQuery

ERDA Google BigQuery users now can select a region for their selected Datasource in both the Reverse Engineer Wizard and the Compare and Merge Utility. Note that you can select only one region. The default selected region is US.

ERDA 201 Reverse Engineering Wizard Selected Region.jpg

ERDA 201 Reverse Engineering Wizard Selected Region 2.jpg

ERDA 201 Compare and Merge Selected Region.jpg

20.1 ER/Studio Team Server Features Summary

Provides a null parent Table and parent Table Primary Key for containment Relationships at the Column level (Table)

The General Properties tab of the Team Server Column description page now provides a null parent Table and parent Table Primary Key for containment Relationships at the Column level.

Adds Data Catalog tree support for Google BigQuery nested objects

Google BigQuery nested objects now appear in the proper format in the ER/Studio Team Server Data Catalog tree. Tables appear in the top order while nested Objects appear under the Columns of the Tables in hierarchy.

Adds options to select version for WhereScape export

WhereScape 3D is adding a feature to check for the source application version. WhereScape users within Team Server now have an option to select the version when exporting XML from WhereScape 3D. The WhereScape Admin Settings page now includes an option to select the Output for WhereScape Versions. Users can choose from the following options:

  • versions 8.6.8.0 and previous
  • versions 8.6.9.0 and above (selected by default)

Improves security of published Diagrams

Team Server 20.1 includes updates to improve security of published Diagrams.

Resolves Collibra and WhereScape integration issues

Resolves an issue where Business Terms connected via a Domain did not display in Team Server but did pass through to Collibra

Team Server 20.1 resolves a Collibra integration issue where Business Terms connected via a Domain did not display in Team Server but did pass through to Collibra.

Resolves an issue preventing Diagram names containing commas from exporting to WhereScape

This release of Team Server resolves a WhereScape integration issue preventing Diagram names containing commas from exporting to WhereScape.

20.0.0 ER/Studio Data Architect Features Summary

Includes an improved Diagram Data Version Upgrade user interface

ER/Studio Data Architect 20.0.0 includes an improved user interface for the Diagram Data Version Upgrade window. This window lets the user know which diagrams within the Repository require an upgrade and provides a checkbox next to each item for the user to select for a bulk update.

Simply check the appropriate box(es), and then click OK to begin upgrading those selected diagrams. Once complete, ERDA lets you know the number of diagrams upgraded, a list of any diagrams that failed, and the overall time taken to perform the process. For more information about this feature, see Diagram Data Version Upgrade.

ERDA 200 Diagram Data Version Upgrade.png

Repository Options dialog box now allows users to select whether to add DDL code to Team Server

The Repository Options dialog box in ER/Studio Data Architect now includes an option under the Team Server selection that allows users to save the Table and/or View DDL to Team Server. The DDL information then appears when viewing the specific Entity type in Team Server. The following options are currently available:

  • Save Table DDL with Physical Models for Team Server
  • Save View DDL with Physical Models for Team Server

For more information about these options and more, see Repository Options Team Server tab.

ERDA 200 Repository Options Save DDL to TS.png

ERDA 200 Repository Options Save DDL to TS Displayed.png

Adds support for comments on View Columns in the View Editor

This release of ER/Studio adds support for comments in the View Columns area of the View Editor. When reverse and forward engineering views or importing views from SQL, the Comments property of the View Column is populated with comments from the database or SQL. This information now appears in the View Editor.

Includes the ability to change a relationship type for containment relationships in Google BigQuery and MongoDB

Google BigQuery and MongoDB users can take advantage of a new feature that allows you to easily change a relationship type for containment relationships. While viewing a containment relationship that you want to change the relationship type, click Switch Relationship Class in the ribbon bar. The following actions occur:

  • If the line is referencing:
    1. ERDA removes the Foreign Key field/column in the child object/table.
    2. A dialog appears asking you to select the desired containing object, and offers Parent, Child, and Cancel options. Note that Child is the default.
    3. ERDA changes the relationship type to containing in the direction selected in the dialog.
    4. A new foreign Key property is created in the Parent object.
  • If the line is containing:
    1. ERDA removes the Foreign Key field/column in the parent object/table.
    2. A dialog appears asking you to select the desired referencing object, and offers Parent, Child, and Cancel options. Note that Parent is the default.
    3. ERDA changes the relationship type to referencing in the direction selected in the dialog.
    4. A new foreign key property is created in the Child object, propagating the primary key of the parent.

For more information about using this type of relationship, see Containment Relationships.

The following image shows this feature using Google BigQuery:

ERDA 200 Switch Relationship Class Google BigQuery.png

The following image shows this feature using MongoDB:

ERDA 200 Switch Relationship Class MongoDB.png

20.0.0 ER/Studio Team Server Features Summary

Adds more details for Primary Key and Foreign Key Columns and Attributes

ER/Studio Team Server 20.0.0 introduces a Relationship tab to the view when you open a page for a Column or Attribute that is a Primary Key (PK) or a Foreign Key (FK). This tab displays a table of relationships to which this Column or Attribute contributes. Note that an FK Column or Attribute has a single relationship while a PK Column or Attribute has multiple relationships.

In addition, when viewing a Column or Attribute that is an FK, Team Server now displays Parent Entity information as well as the Relationship details. You can view the Parent Entity and Parent Table Parent Key used to create the FK property in the General Properties area.

Adds the ability to change Data Source Connection details in the Connection Properties section

Users now can change Data Source connection details, such as the Type and Host Name, using the Connection Properties area of the Data Source page.

ERTS 200 Data Source Connection Properties.jpg

Adds relationships to the Entity, Table, and Submodel pages

Team Server Entity, Table, and Submodel pages now include a section listing all relationships that object has with other objects as well as the nature of those relationships.

The Relationships section include information about the Parent Entity, Child Entity, related PK and FK, relationship Type, and more.

The following image shows this feature for Entities and Tables:

ERTS 200 Entities and Tables Relationships.jpg

The following image shows this feature for Submodels:

ERTS 200 Submodels Relationships.jpg

Improves navigation for fields in a hierarchical structure

This release of Team Server includes improved hierarchy navigation within MongoDB, JSON, and Google Big Query databases. Hyperlinks and including logical names in a table format helps you quickly find what you're looking for with less clicks.

ERTS 200 Hierarchical Improvements.jpg

ERTS 200 Hierarchical Improvements 2.jpg

Adds new tests to the actions performed by the Collibra Test Connection button

When a user clicks the Test button on the Collibra Integration page, Team Server now displays a progress pop-up window that shows which test passed or failed. Detailed errors and responses received from Collibra for these test are stored in the collibra.log file.

ERTS 200 Collibra Test Progress.jpg

These tests include:

  • performing a GET on https://www.idera.com
  • testing for the existence of a Proxy Server
  • testing for the existence of a Team Server keystore file
  • pinging the Collibra server
  • testing the username and password
  • testing the https certificate
  • testing performance (by getting a large block of text)

Updates the Datasources table in ER Objects to display associated Data Assets

This version of ER/Studio Team Server extends the detail available in the ER Objects Datasources table to include Data Asset names and descriptions.

ERTS 200 Datasources Table.jpg

Populates the Last Sync Date in Collibra after each sync

ER/Studio Team Server now updates the Last Sync Date property for Entity, Attribute, Column, Table, and Terms based on their most-recent sync from Team Server, occasionally this occurs whenever a Model is published to Collibra. Note that the Last Sync Date property for Terms is modified only when any property value of the Term changes.

Adds functionality to migrate user license types in bulk

This release of ER/Studio Team Server allows you to migrate user license types in bulk for fast, mass management. In the Licenses view, simply check the box adjacent to the user accounts for which you want to change the License Type. You can use the Select All when needing to migrate all users, but note that this does not include user accounts with Base permission access. Click Select None to clear all user checkbox selections.

In the Bulk Change area, use the drop-down list to select the desired License Type, and then click Set All Selected. Team Server updates the license type for all of those user accounts.

ERTA 200 Migrate User License Types.png

Provides the ability to change Repository settings through the Configurator

ER/Studio Team Server 20.0 Configurator includes an optional Repository Settings page that allows users to manage settings such as customer TLS certificates, non-TLS ports, and enabling a default project.

ERTS 200 Optional Repository Settings Page.jpg

  • Use Custom TLS Certificate. Allows users to have secure Repository communication with ER/Studio Data Architect and Business Architect. Note that TLS communication is automatically available if you choose the TLS option in the Repository Properties page on your client machine. This area also allows you to input your own certificate.
  • Use Custom Non-TLS Ports. Allows users to change the non-TLS ports used for Repository communication. Note that if you use non-default ports, each client must update the settings in the Repository Properties page on your client machines.
  • Enable Default Project. Allows users to select a single Project to which all new Diagrams are added when they are added to the Repository.

Improves performance when managing Submodels and Models

ER/Studio Team Server includes improved performance when:

  • opening a Submodel image or details
  • searching for and loading Models in Collibra and WhereScape

Updates some libraries and framework to the latest version

This release of ER/Studio Team Server includes updates to the latest version of the following products:

  • Apache Log4j
  • Apache Struts
  • Bootstrap
  • jQuery

19.3.5 ER/Studio Data Architect Features Summary

Improves connectivity to multiple Microsoft database platforms

Connectivity to the following Microsoft database platforms is improved in this release of ER/Studio Data Architect:

  • Azure SQL DB
  • Azure SQL Managed Instance
  • Azure Synapse
  • SQL Server

Adds support for Multi-Factor Authentication for Reverse Engineering of Azure SQL DB and Synapse

ER/Studio Data Architect 19.3.5 includes Multi-Factor Authentication (MFA) support for reverse engineering of Microsoft Azure SQL Database and Microsoft Azure Synapse. While generating a script file or database, reverse engineering an existing database, or using the Compare and Merge Utility, Users can choose from new authentication types for the following databases:

  • Microsoft Azure SQL DB and Microsoft Azure Synapse Analytics
    • Active Directory - Managed Identity
    • Azure Active Directory - Integrated (Beta)
    • Azure Active Directory - Password
    • Azure Active Directory - Service Principal
    • Azure Active Directory - Universal with MFA
    • SQL Server Authentication
  • Microsoft SQL Server
    • Active Directory - Managed Identity
    • Azure Active Directory - Password
    • Azure Active Directory - Service Principal
    • Azure Active Directory - Universal with MFA
    • SQL Server Authentication
    • Windows Authentication

For more information about this feature, see Generating a Script File or Database, Reverse Engineering an Existing Database, and Using the Compare and Merge Utility.

19.3.4 ER/Studio Data Architect Features Summary

There are no new features in this release. There are numerous fixed issues that you may review in the Release Notes.

19.3.3 ER/Studio Data Architect Features Summary

There are no new features in this release. There are numerous fixed issues that you may review in the Release Notes.

19.3.3 ER/Studio Team Server Features Summary

Adds support for Azure AD and Okta identity providers via OpenID Connect

Team Server 19.3.3 includes Single Sign On (SSO) support for Azure AD and Okta identity providers that allows you to authenticate your users quickly with your existing database and avoids creation of additional user accounts.

19.3 ER/Studio Data Architect Features Summary

Adds support for Google BigQuery data warehouse

ER/Studio now supports Google BigQuery data warehouse tool. This functionality allows you to reverse engineer a live database, import BigQuery SQL files, and generate both SQL DDL code for new databases and also ALTER scripts through the Compare/Merge tool. This new functionality leverages existing MongoDB and JSON file support, where ER/Studio transforms between relational Logical models to hierarchical Physical models, repeatably handling nested objects to take advantage of BigQuery performance boosts through denormalization.

ER/Studio includes the following improvements to support Google BigQuery data warehouse:

  • Provides support for BigQuery nested field structures. ERDA now includes a number of changes to support the nested field structure of Google BigQuery objects. Updates include:
    • a Nested Object option in the Objects drop-down list
      ERDA 193 BigQuery Nested Object.png
    • Table Objects (Tables) and Fields (Columns) containers in the tree view
      ERDA 193 BigQuery Table Objects and Fields.png
  • Leverages existing capabilities for generation from and Compare/Merge of hierarchical structures with Logical models. Use the Table Editor to easily create and manage your nested objects. If you attempt to create a new object with the same name as an existing object, ERDA allows you to re-use the existing object, create a new object, or skip creating a nested object. Note that when you create a nested object and click Save the object is saved temporarily. You must save the changes to the entire table by clicking OK before the new nested object is created.
  • Adds Data Types and Mappings specific to Google BigQuery. ERDA now includes Data Types and Mapping options specific to Google BigQuery. In addition, an Array optional check box now is available in the Data Type properties area. For more information about this feature, see Customizing Datatype Mappings.
  • Updates the Physical Platforms list to include Google BigQuery. Google BigQuery is added as a new platform to the following flows:
    • Reverse engineering using Simba ODBC DSN
      ERDA 193 Reverse Engineering Using Simba.png
    • Compare against an SQL file
      ERDA 193 Compare and Merge BigQuery.png
    • Add a New Physical Model
      ERDA 193 Compare and Merge BigQuery.png
    • Generate a Physical Model
      ERDA 193 Generate Physical Model BigQuery.png
    • Change Database Platform
      ERDA 193 Change Database Platform BigQuery.png
    • Import Database
      ERDA 193 Import BigQuery.png
  • Updates the Table Editor to support Google BigQuery. The Table Editor has a number of updates to support Google BigQuery including:
    • adding a Clustering Keys option to the Compare Options tab
      ERDA 193 Table Editor Clustering Keys.png
    • adding the Array optional check box in the Data Type properties area
    • updating the Storage tab to support partitioning and allow users to select Partition By Ingestion Time, further specifying by day, hour, month, or year
      ERDA 193 Storage tab.png
    • adding a Clustering tab to allow users to select up to four columns to display
      ERDA 193 Clustering Tab.png
  • Updates the View Editor. The Google BigQuery CREATE VIEW statement now supports the OPTIONS clause. The Options tab allows you to set view options such as a label and an expiration date and time.
    ERDA 193 View Editor.png
    Use the following format noting that VALUE is a constant expression containing only literals, query parameters, and scalar functions:
Name Value Example
expiration_timestamp TIMESTAMP expiration_timestamp=TIMESTAMP "2025-01-01 00:00:00 UTC"
friendly_name STRING friendly_name="my_view"
description STRING description="a view that expires in 2025"
labels ARRAY<STRUCT<STRING,STRING>> labels=[("org_unit","development")]
  • Updates the COM API to allow macros access to support Google BigQuery settings.
Property Type Example
Clustering Keys String Get() - ent.ClusterByColumns() gives the list of selected columns for clustering.

Set() - ent.ClusterByColumns() = "list_of_columns"

Expiration Timestamp STRING Get() - ent.GoogleBigqueryExpirationTimestamp gives the value.

Set() - ent.GoogleBigqueryExpirationTimestamp = "new_value" sets the value.

Partition Expiration Days INTEGER Get() - ent.GoogleBigqueryExpirationTimestamp gives the value.

Set() - ent.GoogleBigqueryExpirationTimestamp= new_number sets the value.

Kms Key Name STRING Get() - ent.GoogleBigqueryKmsKeyName gives the value.

Set() - ent.GoogleBigqueryKmsKeyName = "new_value" sets the value.

Labels STRING Get() - ent.GoogleBigqueryLabels gives the value.

Set() - ent.GoogleBigqueryLabels = "new_value" sets the value.

Partition STRING It has 3 high level classification. NO_PARTITION, PARTITION_BY_INGESTION_TIME,

PARTITION_BY_FIELD For Partition by field, it also contains the column field. For example: PARTITION_BY_FIELD,dummy_date.

Partition Filter STRING It has 2 values. "Y" for boolean True and "" for boolean False.

Get() - ent.GoogleBigqueryPartitionFilter gives the value. Set() - ent.GoogleBigqueryPartitionFilter = "new_value" sets the value.

Partition Type STRING It has 4 values. "BY_DAY", "BY_HOUR", "BY_MONTH", "BY_YEAR"

Get() - ent.GoogleBigqueryPartitionType gives the value. Set() - ent.GoogleBigqueryPartitionType = "new_value" sets the value.

Range Fields STRING All three fields are passed through a string. In this example: "2,4,1" the number 2 is rangeStart, 4 is rangeEnd, and 1 is rangeInterval

Get() - ent.GoogleBigqueryRangeFields gives the value. Set() - ent.GoogleBigqueryRangeFields = "new_value" sets the value.

  • Adds Materialized Views wizard and object type to support google BigQuery. The Materialized Views object is available in the Data Model Explorer for you to view and manage options reflected in generated DDL. Materialized views help improve response time and performance by periodically caching query results and reading only the delta changes from the base tables.
  • Adds procedure, function, and schema object support for Google BigQuery physical models. Users can forward and reverse-engineer, import and generate SQL for, and add/edit/delete procedures in Google BigQuery physical models using the added procedures, functions, and schema object support.
  • Adds support for inheritance. Google BigQuery supports table inheritance and the Generate Physical Model wizard now includes two options for resolving Subtype relationships using the Relationship Type area of the Properties tab:
    • Identifying Relationship
    • Inheritance Relationship
    Note that the inheriting table cannot introduce new columns and remains identical to the inherited table's columns. In addition, Google BigQuery does not allow inheritance of multiple tables nor self-inheritance.
    ERDA 193 Gen Phy Model Relationships.png
    An additional property exists on the physical relationship line of type Inherits that allows you to specify whether it is a LIKE or COPY relationship. If a table is related to another table via an Inherits relationship, then the Column list is ignored during DL generation. In a COPY-type relation, clustering and partitioning options are disabled in the Table Editor.

19.3 ER/Studio Team Server Features Summary

Adds support for Google BigQuery data warehouse

ER/Studio includes many improvements to support Google BigQuery data warehouse.

In Team Server, updates ensure that Google BigQuery Models are rendered correctly from Data Architect into Team Server.

Improves performance when adding a diagram

This release includes updates to the Team Server code to improve performance when users attempt to add a diagram with a large amount of data.

Improves WhereScape Data Automation tool support

ER/Studio Team Server includes the following improvements to support WhereScape Data Automation tool:

  • Swaps the order of extended properties and relations so that extended properties are present before relations.
  • If a table does not include an Index in ER/Studio, then the "indices" element is not present in the table details.

19.2.2 ER/Studio Data Architect Features Summary

There are no new features in this release. There are numerous fixed issues that you may review in the Release Notes.

19.2.2 ER/Studio Team Server Features Summary

There are no new features in this release. There are numerous fixed issues that you may review in the Release Notes.

19.2 ER/Studio Data Architect Features Summary

Improves support for MongoDB

ER/Studio 19.2 includes the following updates to improve support for MongoDB:

Adds support for MongoDB 4.x

ER/Studio 19.2 includes tolerance support for MongoDB 4.0-4.4. For more information about supported databases, see Supported Database Platforms.

Includes SCRAM authentication option as default for MongoDB

The MongoDB Advanced Login Options dialog box includes a change that swaps the positions of the SCRAM and MongoDB-CR options so that SCRAM is selected by default. MongoDB-CR authentication is deprecated and is not included in MongoDB 4.0 and later. For more information about this feature, see MongoDB Advanced Login Options.

192 MongoDB Reverse Engineer Wizard.png

Supports importing JSON Objects from JSON documents

ER/Studio Data Architect lets you create a data model by importing JSON files using a JSON document, in .json or .txt format. Importing these files allows you to create a MongoDB physical model or JSON Instance physical model. For more information about this feature, see Importing a Model from a JSON File.

192 Import Database JSON File.png

Supports switching a MongoDB object's class between Collection and Nested Object

Previously, once a MongoDB physical model is created, objects are fixed as classes of either Collection or Nested Object. ER/Studio 19.2 includes new functionality that allows you to switch a MongoDB object's class between Collection and Nested Object.

Once you select the object you want to switch, click Switch Object Class in the Insert ribbon, as shown in the following image. For more information about this feature, see MongoDB Support.

192 Switch Object Class 2.png

You also can make this switch by using the right-click option on the diagram or the Explorer tree.

192 Switch Object Class.png

Improves Logical to Physical conversion to MongoDB

ER/Studio Data Architect 19.2 includes two new Relationship Type options in the Logical Relationships Editor to allow users to decide the direction of containment relationships. Users can select between the Containing and Parent is Container relationship types. Note that you must select Containing for the Parent is Container checkbox to become active.

You can prevent users from seeing these options by clearing the Show Containment Properties checkbox in the General Options tab of the Logical Model Options dialog box.

These options provide more control for users to select how models are created for MongoDB. For more information about this feature, see Creating and Editing Relationships.

Containment Options.jpg

Improves compare/merge options to MongoDB Physical Models

The Compare and Merge Utility includes new options to support MongoDB Physical Model Collection/Nested Objects and allow users to create new Entities within the utility. For more information about this feature, see Using the Compare and Merge Utility.

192 Compare and Merge Page 3.png

Supports repeated Elements in hierarchical Models

ER/Studio Data Architect 19.2 supports multiple Objects having the same name with different repetition indexes in MongoDB and JSON Instance. This functionality also supports Reverse Engineering in MongoDB.

In the Entity Editor, Compare and Merge Utility, and the Reverse Engineering Wizard, a Repetition Index counter begins at 001 and whenever another repetitive Entity is encountered, the count is increased by 1. This count continues until 999.

In the Reverse Engineering Wizard Page 3, the Handle Repeated Elements option allows you to choose how you want to reverse engineer the elements. Select either Create a new nested object for each or Combine into a single nested object.

Adds Denormalization tools for hierarchical Objects

New Denormalization Tools are available from the Insert ribbon for all hierarchical models. Options include:

  • Rollups
  • Rolldowns
  • Table Merges
  • Horizontal Splits
  • Vertical Splits

Containment relationships are enabled for hierarchical models. when the tables are linked via a containment relationship, the child object is rolled up into the parent. Opposite is true for roll down.

192 Denormalization Tools.png

For more information about this feature, see Optimizing Query Performance on the Physical Model (Denormalizing the Physical Model).

Introduces source code in the Object Editor JSON tab

ERDA 19.2 incudes a new tab for MongoDB and JSON Instance named JSON in place of the DDL tab on the Object Editor. This tab which displays the fields of the context object and all nested objects' fields and nested objects recursively. If the user edits a nested object, its fields and nested objects are included recursively, but no parent information is included. Click Customize and you can manage what content appears in the JSON tab. For more information about the JSON tab, see Customizing Table DDL or Object JSON.

Adds a relationship validity check and display

Relationships that include an error are marked with a universal "no" symbol, as seen below:

Invalid Icon.png

Error conditions include:

  • A referencing relationship where the parent object is a Nested Object and the Parent Key property (Properties tab) of the relationship is Primary Key. If the user changes to an alternate key, then the relationship should be valid.
  • A containment relationship where a Collection is the contained object.

In the following example, the line marked between "address" and "library" did not have the "Containing" flag set, which results in a referencing relationship from the Nested Object. The user then is able to delete the line and recreate using a containment line. Once the issue is resolved, the universal "no" symbol no longer appears.

Invalid Relationship.png

For more information about relationships, see Creating and Editing Relationships.

Includes hierarchical visualization of MongoDB, XML, and JSON

ER/Studio 19.2 includes the following improvements to support a hierarchical visualization of MongoDB, XML, and JSON content:

Provides a roll-up view for hierarchical Models including expand/contract icons and Repeated Object icons for nested Objects

In the ER/Studio Data Architect 19.2 Diagram and Display Options dialog > Object tab, check Roll Up Contained Objects to cause the display of the current submodel to change between the standard graph structure and a rolled-up, nested style. If you choose other submodels in the Apply To tab, this setting also applies to those submodels if they are part of hierarchical models. If Logical submodels and standard RDBMS Physical submodels are selected in the Apply To tab, property changes are applied but do not appear any differently.

Only top-level objects, such as Collections plus any objects that are not contained by another object, remain in the diagram view. For MongoDB models, this includes all Collections but may also include orphaned nested objects. JSON models do not include collections so it would be any object that is not the child of a containment relationship.

For more information about this feature, see Customizing the Display of Diagrams and Objects and Customizing Standard Model Features for New Models.

Object Tab.jpg

Options.jpg

Expand/Contract Icons. The rolled-up view includes expand (+) and contract (-) icons for you to manage your data more effectively.

Repeated Object Icons. Within the rolled-up view, fields that represent nested objects are shown by using the following "repeated object" icons:

  • Unique to Parent.png Unique to parent.
  • Used Elsewhere.png Used elsewhere. i.e. has other containment relationships that are contained within.

Note that some nested objects can appear under multiple parent objects (Collections or other Nested Objects), but others are unique to single parent objects.

Roll-Up.png

Keyboard Entry Tools. Another feature of the rolled-up view is functionality that allows you to quickly add and modify fields to a nested structure inside the rolled-up view for hierarchical models. Simply press ENTER on your keyboard, and a dialog appears to allow you to select options for nested objects. Note that the Array checkbox is only for MongoDB and JSON platforms.

Move Functionality. Use the Move (cursor finger) function to move Attributes/Columns from one Entity/Table to another or move within an entity or view. Other attributes of the Move functionality include:

  • When used within a Collection, you can move a Field within a containing parent object or across parent objects.
  • When you move a Field that is an FK field for a containment relationship, all substructures move with it. This also allows for the movement of nested objects between Collections.
  • When you move a Field that is an FK field for a referencing relationship, a copy of that field is made as per current behavior, leaving the existing FK unchanged.

Allows users to set data types during In Place Editing

New functionality allows users to set data types while editing /adding a column using SHIFT+CLICK. You can enable/disable this feature using Allow set data types dialog in the Options dialog for Diagrams, accessible by clicking Tools > Options > Diagram. For more information about this feature, see Customizing Standard Model Features for New Models.

Options Diagram.jpg

Provides parent/child Entity switch icon in Table Editor

Using the Switch icon (Switch Icon.png) in the Table Editor, you can easily switch the view from child Entity to parent Entity for that selected row.

Switch Child Parent.png

Supports JSON Instance files

ER/Studio 19.2 includes tolerance support for JSON Instance. For more information about supported databases, see Supported Database Platforms.

Allows users to switch between MongoDB and JSON Instance hierarchical platforms

Users now can switch the database platform of a physical data model ONLY between hierarchical model platforms. Use Change Database Platform to switch from MongoDB to JSON Instance and vice versa, but not to any non-hierarchical platforms.

Change Database Platform.png

19.2 ER/Studio Team Server Features Summary

Includes several Data Catalog improvements

ER/Studio Team Server includes a few improvements to the Data Catalog including:

  • Adding a new Data Asset Object Type
  • Renaming the Data Sources tab to Data Catalog and providing a default hierarchical tree view of deployed data assets
  • Removing the Test Connection button from Data Catalog tab
  • Adding the Hide Login Credentials checkbox to My Settings > Admin, allowing users to prevent the Login Credentials section from appearing in the main view

This release introduces a new Object Type called Data Asset. While Data Sources are objects such as database servers, network folder locations, and Amazon S3 buckets, Data Assets consist of database instances or files/messages. Data Assets are first class Objects, so that you can attach custom properties to it and maintain a visible catalog of assets without the need to assign a physical model to each.

ERTA 192 Data Assets Tree.png

In support of introducing the Data Asset Object Type, we renamed the Data Sources tab to Data Catalog and provide a default hierarchical tree view of deployed Data Assets, as shown in the following image.

ERTS 192 Data Catalog.png

Notepad blue icon 2.pngNote: Data Assets can exist only within a Data Source. While you can create Data Assets without a Physical Data Model, you can attach them to a single Physical Data Model.

We also removed the Test Connection button from the Data Catalog tab and added a Hide Login Credentials checkbox to My Settings > Admin to prevent the Login Credentials section from appearing in the main view.

Improves Oracle Performance

This release includes updates to the Team Server application code to improve Oracle performance.

Glossary Improvements

Several improvements were made to update Glossary support, including introducing the Business Glossary Report, which provides a list of Glossaries with descriptions and Business Terms related by the "is part of" and "is related to" relationships to one or more Parent Glossaries.

19.1.1 ER/Studio Data Architect Features Summary

There are no new features in this release. There are numerous fixed issues that you may review in the Release Notes.

19.1.1 ER/Studio Team Server Features Summary

Integrates with WhereScape Data Automation Tool

ER/Studio Team Server 19.1.1 begins integration with WhereScape Data Automation tool, which allows data warehouse architects to automate the design, creation, and operation of a data warehouse.

Adds built-in properties for Collibra integration for columns and attributes

ER/Studio Team Server 19.1.1 improves Collibra integration by adding the following built-in properties for column and attributes:

  • Datatype (text)
  • Width (numeric)
  • Scale (numeric)
  • Allow Nulls (Boolean)
  • Is Primary Key (Boolean)
  • Is Foreign Key (Boolean)
  • Sequence (numeric)

19.1 ER/Studio Data Architect Features Summary

Adds support for multiple Oracle 12c and later features

ER/Studio Data Architect 19.1 includes support for the following features in Oracle 12c and later:

  • External tables. External tables allow Oracle to query data stored outside of the database in flat files. Use the Table Editor option to designate an external table and gain access to the External Table Properties dialog for further definition of the table. For more information about this feature, see Defining Table Storage: Oracle 12c and Later Storage Options.
  • Subpartitioning by RANGE. Range partitioning distributes data based on a given range, as in time intervals and allows you to easily add new data while purging older data. For more information about this feature, see Subpartition Editor.
  • Identity columns. Identity columns allow you to auto-increment values each time you add a row. You can set only those columns having a Data Type of Number as identity columns, and you may have only one Identity column per table. For more information about this feature, see Creating and Editing Columns: Datatype tab.

Adds support for multiple Oracle 11g and later features

ER/Studio Data Architect 19.1 includes support for the following features in Oracle 11g and later:

  • Interval partitioning. Interval partitioning automatically partitions a database at specified intervals when new data added to the table exceeds all of the specified range partitions to avoid insert failures. Use the Partition tab of the Table Editor to set what interval is in use. For more information on this feature, see Partitioning a Table: Table Partition Options for Oracle.
  • Reference partitioning. Reference partitioning allows you to partition two tables that are related based on an existing parent-child relationship. You can manage partition keys and types on the Partition tab of the Table Editor. For more information on this feature, see Partitioning a Table: Table Partition Options for Oracle.

19.1 ER/Studio Team Server Features Summary

Improves workflow for adding custom properties to selected objects

Team Server 19.1 allows the Team Server admin to add custom properties to selected objects in Team Server without using Enterprise Data Dictionary attachments or the Repository. Note that the Managed Attachment Attributes page now is renamed Custom Properties.

Allows user to specify a backup folder location when upgrading

Team Server 19.1 now allows users to specify the backup folder location to use when upgrading Team Server.

Includes support for a hyperlinked URL on a Term Custom Attribute

While Team Server already allows users to add a URL to a Term Custom Attribute, this version provides the ability for the URL to include a clickable hyperlink.

Allows the Team Server admin to hide menu items based on user group

Team Server 19.1 includes an option for an administrator to hide specific menu items, such as Glossary, People, Data Sources, etc., based on user group.

191 Menu Visibility.jpg

See Also