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:

21.0.0 ER/Studio Data Architect Features Summary

Updates ER/Studio branding

ER/Studio 21.0 introduces new and more modern branding in many areas of the products. You'll notice new colors, icons, and updated wizards and dialogs.

Introduces the AI Chatbot

This release of Data Architect provides additional assistance to user through use of the AI Help Chatbot. Accessed by clicking the question mark Help icon in the upper right-hand corner of the window, users can ask specific questions regarding the product and its use. The AI Help Chatbot then works with the user to find exactly what they are searching for. For more information about using this feature, see Using the AI Help Chatbot.

Adds support for Replica Tables and Replica Views

This release of ER/Studio Data Architect introduces support for cross-database references of Database.Schema.Table (Replica Table) and Database.Schema.View (Replica View) for the following database platforms:

  • Azure Synapse Analytics
  • Snowflake
  • SQL Server 2019 and 2022

This feature allows users to work with Replica Tables and Replica Views and supports reverse engineering of external dependencies for Views.

For more information, see Creating and Editing Replica Tables and Replica Views.

Using Replica Tables and Replica Views

Insert Replica Tables and Replica Views into your Diagrams from the Insert > Objects > Replica Table or Replica View menu. Once a Replica Table or Replica View is in your diagram, notice that these objects include a think, dashed border with a different-colored background.

ERDA 210 - Replica Table Menu Items.png

Users also can switch an Object between a Replica Table and a normal Table, as well as the same with Replica Views. Simply click to highlight the Table or View you want to switch, and then click Switch Object Class from the Insert ribbon menu. You can also use the context menu by right clicking on the Object in the Data Explorer tree, and then selecting Switch Object Class > Switch to Regular Table/Regular View or Switch to Replica Table/Replica View. Use Undo/Redo to return to the previous state.

ERDA 210 - Replica Table Switch Object Class.png

Notepad blue icon 2.pngNote:

  • Switching from Regular Table/Regular View to Replica Table/Replica View causes a loss of all data associated with hidden properties, and regular relationships except for view relationships also are lost.
  • Switching from Replica Table/Replica View to Regular Table/Regular View returns hidden properties but with the default values as if it is a new Table/View.

Both Replica Tables and Replica Views are available in the Automation Interface. For more information about this interface, see Automating ER/Studio Data Architect.

Understanding Replica Tables

Replica Tables include the following properties:

  • offers only a limited number of tabs in the Replica Table Editor
  • users can change Definition, Notes, and Glossary properties only
  • Owner property of table is populated with databaseName.schemaName by default

ERDA 210 - Replica Table Editor.png

Use reverse engineering to add a Replica Table when representing a Table outside of the selected database or use the Compare/Merge feature to add a Replica Table from another Physical Model.

Replica Tables cannot be a parent or child of a relationship. However, Data Architect allows Replica Table view relationships from non-replica views in the model if those views reference this Replica Table.

Understanding Replica Views

Replica Views include the following properties:

  • offers only a limited number of tabs in the Replica Table Editor
  • Owner property of table is populated with databaseName.schemaName by default

ERDA 210 - Replica View Editor.png

If the DDL is correct, a Replica View is validated no matter whether the referenced Objects are in the current Model.

Note that you cannot edit within the Columns tab. It is read-only and populated with the Columns parsed from the DDL. You can make changes to the DDL directly in the DDL tab.

View relationships are allowed from non-replica views in the model if those views reference this Replica View.

Using reverse engineering for Replica Tables and Replica Views

Users with the following permissions can reverse engineer Replica Tables and Replica Views:

  • On the current database:
    • SELECT and VIEW DEFINITION on the sys schema
    • SELECT and VIEW DEFINITION on the selected schema
  • On the referenced databases, i.e. where the View's dependencies reside:
    • SELECT and VIEW DEFINITION on both the referenced schema and the sys schema

Notepad blue icon 2.pngNote: This functionality supports only external databases within the same SQL Server instance. Cross-referenced database references are no supported.

Generating a database for Replica Objects

When Generating a Script File or Database with Replica Tables or Replica Views, note that the Replica Objects do not appear on Page 3 of the Wizard in the tree view for Tables and Views, and therefore no SQL preview is available.

Notepad blue icon 2.pngNote: DDL is available for Replica Views only. Replica Tables display n/a.

Using the Compare and Merge Utility with Replica Objects

When Using the Compare and Merge Utility with Replica Tables or Replica Views, you can see the graphical differences between Models having and not having Replica Objects while viewing Page 5 of the Wizard. The Model that has a Replica Table or Replica View appears with the replica icon ICON - Replica Table or View.png.

ERDA 210 - Replica Table Compare Merge.png

Click SQL Difference and you notice that you see only those properties and folders associated with Replica Objects no matter what type of Object is on the other side.

You cannot merge Replica Objects into Regular Objects. For example, if the source contains Replica Objects and the target is a Regular Table or Regular View, then using Merge into Target from the dropdown list automatically switches the Resolution to Ignore. Conversely, if the source contains Regular Objects and the target is a Replica Table or Replica View, then using Merge into Current from the dropdown list also automatically switches the Resolution to Ignore.

Notepad blue icon 2.pngNote: You cannot generate alter script for Replica Objects even if you select the option to generate SQL.

Understanding Replica Object data lineage

If you compare a Model in another dm1 using the Import Source Wizard (Other Sources > Import New Source > From a model in another dm1), no Replica Objects appear beginning on Page 4 of the Wizard.

Saving only Replica Matches

In the Save Matches Options dialog, accessible from Page 5 of the Compare and Merge Utility by checking the Save Matches box, and then clicking the ellipses button in the bottom-right corner, you can create mappings only for Replica Objects by selecting the Save only replica matches option.

ERDA 210 - Replica Table Compare Merge Save Matches.png

When this option is selected, the system save only those matches between Replica Objects and Regular Objects. You can identify Replica Mappings by the unique icon on the Where Used tab of the Table/View Editor.

Notepad blue icon 2.pngNote: If a universal mapping already exists between a Replica Table or Replica View and a Regular Table or Regular View and you select the Save only replica matches option, the mapping converts to a Replica Mapping.

A Replica Object can have only one Replica Mapping with a Regular Object. If a Replica Object already has a Replica Mapping, and you attempt to map it to another Regular Object, the existing Replica Mapping converts to a Universal Mapping and a new Replica Mapping is created for the new match.

Improves repository security by allowing ERDA to log in via SSO using Okta

Enterprise users who have Okta configured in Team Server now can log into Team Server and repository from Data Architect via SSO using Okta. For more information, see Logging In and Out of the Repository and ER/Studio TS.

Adds support for TLS 1.3

ER/Studio Data Architect and Repository 21.0 now use TLS 1.3 as the default protocol for all secure communications. This support includes the following cipher suites:

  • TLS_AES_128_GCM_SHA256 Enabled by default.
  • TLS_AES_256_GCM_SHA384 Enabled by default.
  • TLS_CHACHA20_POLY1305_SHA256 Enabled by default.
  • TLS_AES_128_CCM_SHA256

Configuring a TLS cipher suite

You can control which TLS cipher suite is used by configuring the TLS Ciphers registry setting.

Registries are located at:

  • ER/Studio Data Architect Client
    HKEY_CURRENT_USER\Software\Idera\ER/Studio Data Architect 21.0\Repository
  • Repository Server
    HKEY_LOCAL_MACHINE\SOFTWARE\Idera\Repository\Database

Notepad blue icon 2.pngNote:

  • To configure one of the default supported cipher suites, you must set the cipher in the client-side registry.
  • To use TLS_AES_128_CCM_SHA256, the cipher must be explicitly configured in both the client-side and server-side registries.

21.0.0 ER/Studio Team Server Features Summary

Updates ER/Studio branding

ER/Studio 21.0 introduces new and more modern branding in many areas of the products. You'll notice new colors, icons, and updated wizards and dialogs.

20.9.1 ER/Studio Data Architect / 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.

20.9.0 ER/Studio Data Architect Features Summary

Supports JSON complex columns in traditional databases

This release of ER/Studio Data Architect allows you to reverse engineer and model embedded JSON data in standard RDBMS platforms including:

  • Azure SQL DB
  • Azure Synapse Analytics
  • Microsoft SQL Server 2019, 2022
  • Oracle 19c, 23ai
  • PostgreSQL
  • Snowflake

This feature allows you to take advantage of the flexibility of JSON while also providing improved data documentation and governance. You can map the fields in the embedded JSON to Business Terms and populate the data catalog. For more information about how ERDA supports JSON, see JSON Support.

In Data Modeling

For the platforms listed above, ERDA 20.9 includes the ability to create and model Nested Objects and Containment Relationships.

Notepad blue icon 2.pngNote: You can create containment relationships only between Table and Nested Object, and between Nested Object and Nested Object. Non-containment relationships are not allowed.

Click Insert > Objects > Nested Object.

ERDA 209 Nested Objects for JSON Complex Columns.png

Or click Insert > Relationships > Containment Relationship.

ERDA 209 Containment Relationship for JSON Complex Columns.png

This release also introduces the following JSON datatypes for Nested Objects but not Tables:

  • JSON_BOOLEAN
  • JSON_INTEGER
  • JSON_NUMBER
  • JSON_OBJECT
  • JSON_STRING

If you open older version files in this version, you must follow a few steps to enable the new JSON datatypes. To enable new JSON datatypes in existing models, click Model > Model options > Update Datatype Mapping. Once you click, the system updates the existing mappings and applies the new data types. To enable these new data types in the Domain Editor, you must update the data type mapping in the Logical model to use the new mappings.

Users also can switch the Object Class and Relationship Class for existing relationships. When viewing the item you want to switch, click Insert > Switch Object Class or click Insert > Switch Relationship Class. For more information about switching relationship classes, see Changing a relationship type for containment relationships.

Generating a Physical Model from a Logical Model

You can specify how you want Tables created from Logical Entities in the Generate Physical Model and Compare and Merge Utility wizards. Select from the following options:

  • Create All as Tables. Use this option to create all entities as regular tables and ignore containment.
  • Create as Tables unless Contained. When selected, this option converts any relationship marked as "containing" in the logical model into a containment relationship, and the contained entities are generated as Nested Objects.

ERDA 209 Generate Physical Model for JSON Cojmplex Columns.png

ERDA 209 Compare and Merge Logical.png

Based on the supported database platform, you can define what data appears in your standard Tables and Columns while also generating SQL code as well as JSON Schemas and sample instance files.

In addition to the table structure, ERDA now reads in data, one record (row) at a time, including all columns of the specified data types, and excluding the rest. All relevant columns are combined into one JSON structure for efficiency. This JSON structure is then parsed, and Nested objects are created based on the contents.

For SQL Server, we have a size limit of 1MB for data of all relevant columns from one record. If data from a single record exceeds this limit, it is truncated to 1MB. Any JSON structures which are fully read in are used to generate Nested Objects. Those JSON structures that are truncated, or are not read in at all, as they occur in later columns, are not generated. You may receive the following warning message: 

Table: <table_name>, Record: <row#> - Some of the JSON data may be truncated because it exceeds the maximum length.

For columns that are marked as valid JSON data types, but do not have any JSON structure data in them, you may receive the following warning message: 

No valid JSON found in sample for <table_name>.<column_name>

The following fields are available in the Reverse Engineer and Compare and Merge Utility wizards for this feature:

  • Check the appropriate data types of columns that may store JSON data. The available data types vary depending on the database platform, e.g., variant, object, and array for Snowflake, varchar and nvarchar for SQL Server, etc.
  • Number of records to parse. Select how many records you want to parse. You may want a large number as you may have some records that contain JSON with incomplete sets of fields and parsing additional records can provide a complete set.

Reverse Engineer new options.png

ERDA 209 Compare and Merge Reverse.png

Notepad blue icon 2.pngNote: Select Combine into single nested object as you may be interested in common objects across those JSON structures and want them combined into a simple set.

For more information about this feature, see Reverse engineer embedded JSON structures

Generating JSON Instance / Schema files

Users also can generate JSON Instance / Schema files for embedded JSON using the Generate Database wizard. In the Generate Database wizard, if you select Generate single ordered file or Generate Objects to Multiple files, then the JSON options shown in the following image are enabled.

ERDA 209 Generate JSON Instance Scehma Files.png

If you select other generation options, such as Generate with a Database Connection or Generate a Script file to Git,, the Ignore option is selected and the other JSON options are disabled.

For each table selected in the Tables tab, the top-level nested objects are generated as JSON files:

  • For the Generate single order file option:
    • A new folder is created (if it does not exist) inside the directory where the DDL is generated with the same name as that of the DDL file.
    • The JSON files are generated in this newly-created folder.
  • For the Generate Objects to Multiple files option:
    • A new folder called JSON is created inside the Tables directory of the base directory. This folder contains the generated JSON files.
  • If the file or folder already exists, an appropriate warning message is displayed.

ERDA 209 JSON File ID.png

20.9.0 ER/Studio Team Server Features Summary

Adds the ability for Data Architect to communicate with Team Server Repository via IPv6

ER/Studio 20.9 allows Data Architect to connect to Team Server Repository using IPv6. While in Data Architect, users can log in to Team Server using IPv4 or IPv6 protocol. To change from the default IPv4 option, navigate to the Repository Settings page, and then select IPv6 from the Internet Protocol dropdown list. Click Update to save your change.

ERTS 209 IPv6 selection.png

Allows users to select the master source for Terms / ER Objects relationship mapping as either Collibra or Team Server

Users now can select whether Collibra or Team Server is the master for relationships between Terms and ER Objects. Simply go to My Settings > Collibra > Settings and find Master for changes to Term to ER Object Relationships in the Collibra Config section, and toggle between the default Team Server and Collibra.

ERTS 209 Whats New Collibra Settings.png

Provides Team Server database authentication via Azure Manifest Certificates for Azure SQL Database

ER/Studio increases enterprise-level security by providing Azure SQL Database users authentication via Azure Manifest Certificates. Make sure Manifest Certification Authorization is selected on the Repository DB Setup page of the installation or configuration wizard.

ERTS 209 Manifest Certificates 1.png

20.8.1 Team Server Features Summary

Improves support for the Trust Server Certificate parameter in SQL Server and Azure SQL environments

ER/Studio Team Server 20.8.1 is a minor release that includes the final implementation of support for the Trust Server Certificate parameter in MS SQL Server and Azure SQL connection flows. The enhancement allows users to bypass SSL/TLS certificate validation when connecting to SQL Server instances using self-signed or untrusted certificates, with additional handling introduced for Windows Authentication scenario via updates to the ER/Studio Launcher.

The Trust server certificate option now appears in the Repository DB Setup page of the Team Server Configurator for users who select MS SQL Server 2012-2022 or MS Azure SQL DB / MS Azure SQL Managed Instance. By default, this checkbox is clear.

20.8.0 ER/Studio Data Architect Features Summary

Introduces AI Model Builder capabilities

ER/Studio Data Architect 20.8 allows you to create a logical data model using a block of text. This feature is available by clicking Generate Using AI when creating a new file or by clicking the AI Model Builder button in the Tools ribbon bar, as shown in the following image. Note that the Welcome Page also offers a link to generate a model using AI.

ERDA 208 Generate Using AI Options.png


Warning.gif WARNING: The accuracy of data models generated using AI is not guaranteed. Any content generated using this tool must be separately reviewed and verified by a human.

The AI Model Builder dialog allows you to type prompts for the tool to create a new model. Click Surprise Me to include an example prompt so that you can get an idea of what information and format helps the AI build a good model. The following example was generated using the Surprise Me button and explains how to build a database to manage a large-scale event planning and ticketing platform.

ERDA 208 AI Model Builder Surprise Me Text.png

When finished model generation, the AI Model Builder displays your new model in the background while also displaying a robust description of the model in the AI Model Builder Progress dialog.

ERDA 208 Generating AI Model Finished.png

For more information about this new feature, see Generating a Model Using AI.

20.8.0 ER/Studio Team Server Features Summary

Adds security improvements

This release of Team Server includes various updates to improve security across the product.

20.7.0 ER/Studio Data Architect Features Summary

Adds support for JSON Examples field

ER/Studio Data Architect 20.7 includes improvements for the JSON Instance database platform by now supporting "examples," which is a list of example values accepted by a field. Example values appear Datatype Properties section of the Datatype tab.

ERDA 207 JSON Examples Field.png

Click the edit (...) button to the right of the Examples field, and the Examples dialog appears for you to add, edit, or delete JSON examples available for the selected field. Examples values entered in this dialog are used in JSON schema and JSON instance generation.

ERDA 207 JSON Examples Dialog.png

When creating or editing a table, MongoDB and JSON Instance users may note a JSON tab which displays the JSON schema or JSON Instance. For JSON Instance, each field contains the default value, or first examples value, or first reference value, in that order of preference.

ERDA 207 JSON Tab Example Output.png

When using the DDL Generation Wizard to generate JSON code to build a MongoDB database, note the actions of the following options:

  • For JSON Instance, each field contains the default value, or first examples value, or first reference value, in that order of preference.
  • For JSON Schema, the default value, and all examples and reference values are included.

ERDA 207 MongoDB JSON Generation Preview.png

For more information about this topic, see Creating and Editing Columns, Creating and Editing Tables, and MongoDB JSON Generation.

20.7.0 ER/Studio Team Server Features Summary

Improves Team Server's Purview functionality

ER/Studio Team Server includes improved support for Microsoft Purview by adding functionality for the new Business Domain Glossary Terms to support Data Mesh Product design. One important item is that to synchronize new Business Domains with Team Server, each Business Domain on the Purview side must include users in the following roles:

  • Data Steward
  • Data Catalog Reader

20.6.0 ER/Studio Data Architect Features Summary

Provides workflow macros to generate Data Vault assets from model objects

This release of ER/Studio Data Architect includes new workflow macros that generate Data Vault assets from model objects to help you design schemas for data warehousing. For more information about this product and its Data Vault features, see Using Data Vault Tools.

Adds support for external tables in Azure SQL DB, Azure Synapse, and SQL Server

This release of ER/Studio Data Architect supports external tables in Microsoft's SQL Server 2019 and 2022, Azure SQL DB, and Azure Synapse platforms to pull data from an external source upon a DML read. Note that before you can create an external table, you must create an external file format and an external data source.

An external table has fewer features than a normal table. Once a table is set as an external table in ERDA, many properties are disabled or hidden, except for the following:

  • Primary Keys
  • Foreign Keys
  • Relationships with other tables

For more information abut this feature, see External Table Properties.

Adds support for SQL Server 2022

ER/Studio Data Architect now supports Microsoft SQL Server 2022 database platform. For more information about supported databases, see Supported Database Platforms.

Adds support for Oracle 23ai / 23c

ER/Studio Data Architect now supports Oracle 23ai / 23c database platform. For more information about supported databases, see Supported Database Platforms.

Adds the Switch Object Class button for Databricks and Google BigQuery

This release of ER/Studio Data Architect includes a button to Switch Object Class to convert a Nested Object to a Table and vice versa in Databricks and Google BigQuery. Use this option on the ribbon bar of the Insert tab or by right-clicking an object in the explorer tree, and then selecting Switch Object Class, or if using the Automation Interface, by the SwitchObjectClass method in the Entity object.

ERDA 206 Switch Object Class.png

20.6.0 ER/Studio Team Server Features Summary

Adds security improvements

This release of Team Server includes various updates to improve security across the product.

20.5.1 ER/Studio Data Architect Features Summary

Adds support for PostgreSQL up to version 16.x

ER/Studio Data Architect now includes support for PostgreSQL up to version 16, which allows for include columns. Use the Options tab of the Index Editor to add columns in the Include field. For more information about including columns for PostgreSQL, see PostgreSQL Index Options. For more information about available platforms, see Supported Database Platforms.

Improves support for Google BigQuery

Current ER/Studio Data Architect support for Google BigQuery is expanded by adding features for Primary Key, Foreign Key, Search index, and column defaults. A new Add to Primary Key option appears in the Columns tab of the Table Editor. For more information about using this feature, see Columns tab, DDL tab, and Google BigQuery Options.

For more information about available platforms, see Supported Database Platforms.

Improves support for Snowflake

This release of ER/Studio Data Architect improves Snowflake-related features by adding support for:

  • CTE views. Adds CTE Views in the With (CTE) tab of the View Editor. For more information, see With (CTE) tab.
  • Hybrid tables. Allows you to create hybrid tables for expanded versatility within your environment. For more information, see Using Hybrid Tables.
  • Extended properties for a Primary Key Constraint. Supports extended properties for Snowflake Primary Key constraints. These properties help when migrating from other databases. For more information, see Snowflake Index Options.

For more information about available platforms, see Supported Database Platforms.

Improves repository security by allowing ERDA to log in via SSO using Microsoft Entra ID

Enterprise users will notice new repository security improvements by allowing Data Architect users to log into Team Server and repository via SSO using Microsoft Entra ID. For more information, see Logging In and Out of the Repository and ER/Studio TS.

20.5.1 ER/Studio Team Server Features Summary

Expands Team Server API functionality

This release includes improvements to the Team Server API to fetch Delta changes to model objects.

Includes Team Server security improvements

ER/Studio Team Server now includes updates to database access components to improve security.

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

20.3 ER/Studio Data Architect Features Summary

Adds support for Git

ER/Studio Data Architect 20.3 allows you to deploy a Devops process by integrating Data Architect with your Git repository. This feature allows you to commit CREATE DDL to your Git repository as well as use the Compare/Merge functionality to compare models with previous versions of that CREATE DDL in your Git repository. You can get started in setting up your Git integration by clicking the Git Options button in the Tools menu. You must be in the Physical Model view for this option to appear.

For more information about this feature, see Integrating with Git.

20.3 ER/Studio Team Server Features Summary

Adds support for RSA SecureID single sign-on (SSO)

This release of ER/Studio Team Server includes support for RSA SecureID single sign-on (SSO). In the Configurator, select Use SSO, and then select RSA Secure ID from the Select SSO Provider list. Note that the fields change based on this selection. Be sure to complete these fields as necessary for your SSO provider.

ERTS Configurator Single Sign-On RSA Whats New.png

Updates the user experience to connect with Okta SSO

ER/Studio's support of Okta SSO is expanded, with the ability for users to manage dynamic Authorization and Scope data. These details are added during setup using the Team Server Configurator or managed using the process available in Configuring Your Okta SSO Provider.

Adds support for a Service principal account

ER/Studio Team Server now supports a Service principal account for Microsoft Entra as an alternative to basic authentication for the Team Server backend database. In the Configurator, select MS Azure SQL DB. Notice the Service Principal Authentication check box and associated fields appear. Note that the user account adding this information must have Create database privileges. In addition, the user account must have the Log on as a service permission on the local app server as the Repository services are changed to run under that account in order to connect to the database using Service Principal authentication. If the account does not have this permission, you will receive an error when testing the connection.

ERTS 203 Service Principal Auth.png

Complete the following fields:

  • Client ID and Client Secret. Type the Azure AD service principal client ID and secret.
  • Database. Specify the name of the database that you want to create for a new installation or update the name in the case of an upgrade.

Once you complete these fields, click Test to verify your entries. Click Next to continue.

Improves Security Audit Trail reporting

Security Audit logging in Team Server is improved with this release. In the Configurator, go to the Repository Setting page, and then check the box for Enable Activity Logs to enable additional audit logging of model changes and security updates. Make sure to click Next, and then finish the Configurator for the changes to take effect. If modifying settings for an already configured installation, click Update. When that update completes you must open services.msc, then stop the Idera Repository Database Server service, wait 1-2 minutes for the RepoSrvDb.exe process to close, and then start the same service again.

20.2 ER/Studio Data Architect Features Summary

Adds support for Databricks database platform

ER/Studio Data Architect 20.2 includes a number of updates to support the Databricks database platform as a core platform, including basic constructs plus enhanced workflow capabilities. This functionality requires the installation of the Databricks ODBC driver, which allows reverse engineering operations to the Unity Data Catalog. Note that this implementation is based on the UDC version of Databricks and thus supports advanced features such as primary/foreign key constraints.

Databricks constructs for this release include:

Enhanced workflow capabilities include:

For more information about this feature, see Databricks Support.

20.2 ER/Studio Team Server Features Summary

Introduces support for Microsoft Purview

ER/Studio Team Server introduces support for Microsoft Purview data governance tool. This support includes:

  • Synchronization of Business Terms
  • Publication of Logical data models including mappings to Terms
  • Documentation of scanned assets from Physical data models with mappings to Terms and to Logical data models

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

See also

Retrieved from "https://docwiki.embarcadero.com/ERStudioDA/210/e/index.php?title=What%27s_New&oldid=9080"