Thank you for using IDERA ER/Studio Viewer. ER/Studio Viewer provides to anyone outside of the data modeling team an interactive environment for viewing ER/Studio data models. This distributable application provides the same sophisticated and advanced viewing features offered to modelers through the native ER/Studio application. Why rely on static representations and graphical snapshots that are difficult to navigate and find information? ER/Studio Viewer displays the same DM1 model file generated by the native ER/Studio application. This enables the Viewer to provide all of the data model's underlying information, such as table and column definitions, in the same accessible format as ER/Studio. To ensure data integrity and security, ER/Studio Viewer offers no editing capabilities preventing unauthorized modifications to the DM1 file.
See the most recent documentation at the IDERA Web site, https://www.idera.com/support/productdocuments
WHAT'S NEW in version 19.3
WHAT'S NEW in version 19.2
WHAT'S NEW in version 19.1
WHAT'S NEW in version 19.0.1
WHAT'S NEW in version 19.0
ER/Studio Viewer Features
This release of ER/Studio includes many improvements to support Google BigQuery data warehouse.
· Provides support for BigQuery nested field structures.
· Leverages existing capabilities for generation from and Compare/Merge of hierarchical structures with Logical models
· Adds Data Types and Mappings specific to Google BigQuery.
· Updates the Physical Platforms list to include Google BigQuery.
· Updates the Table Editor to support Google BigQuery including:
o changes to the Table Editor Storage Tab
o adds a Clustering Tab
· Updates the View Editor.
· Updates the COM API to allow macros access to support Google BigQuery settings.
· Updates the Reverse Engineering Wizard.
· Updates the Import SQL File Wizard.
· Updates the DDL Generation Wizard.
· Updates the Compare and Merge Wizard.
· Adds Materialized Views.
· Adds procedure support for Google BigQuery physical models.
· Adds function support for Google BigQuery physical models.
· Adds schema object support for Google BigQuery physical models.
· Adds support for inheritance
This release of ER/Studio Data Architect includes many improvements to support MongoDB and JSON Instance.
· Adds support for MongoDB 4.x
· Includes SCRAM authentication option as default for MongoDB
· Supports importing JSON Objects from JSON documents
· Supports switching a MongoDB object's class between Collection and Nested Object
· Improves Logical to Physical conversion to MongoDB
· Improves compare/merge options to MongoDB Physical Models
· Supports repeated Elements in hierarchical Models
· Adds Denormalization tools for hierarchical Objects
· Adds source code to the Object Editor DDL tab
· Adds a relationship validity check and display
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
· Provides a roll-up Contained Objects view for hierarchical Models
· Provides Repeated Object icons for nested Objects
· Provides Expand/Contract icons for roll-up views
· Allows users to set data types during In Place Editing
· Provides keyboard entry tools for roll-up views
· Supports Move function for roll-up views
· Provides parent/child Entity switch icon in Table Editor
ER/Studio 19.2 includes tolerance support for JSON Instance.
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.
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.
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.
ER/Studio Data Architect 19.0.1 includes additional support for SQL Server Temporal Tables, allowing users to designate in-memory tables and have Data Architect check whether the columns are suitable as not all datatypes are supported for in-memory. For more information about this feature, see Microsoft SQL Server Table Storage Options.
This release includes the addition of the Switch Windows button in the Diagram ribbon. This button allows the user to switch and view each of the different open files.
The new Universal Mappings button on the Repository ribbon allows users to create links between objects across models, which are visible in the Where Used tab of Objects and in Team Server Core.
The new Diagram Properties button on the Model ribbon allows users to easily set properties for the diagram file.
New options allow users to select how the plain JSON output is generated from MongoDB-specific content. For more information about this feature, see MongoDB JSON Generation.
This version of ER/Studio Data Architect supports Azure Active Directory – Password as an authentication method in Azure SQL Database available in the following scenarios:
engineering objects from Azure SQL Database with a direct connection.
In the Authentication field of the Reverse Engineering Wizard, select the Azure Active Directory – Password option. For more information about this feature, see Reverse Engineering an Existing Database.
engineering to Azure SQL Database using a direct connection.
In the Authentication field of the DDL Generation Wizard, select the Azure Active Directory – Password option. For more information about this feature, see Generating a Script File or Database.
with a live database for Azure SQL Database using a direct
In the Authentication field of the Compare and Merge Utility, select the Azure Active Directory – Password option. For more information about this feature, see Using the Compare and Merge Utility.
The separate Repository and Team Server login menu buttons and dialog boxes now are combined, allowing users to optionally connect to Repository and Team Server at the same time. The single Log In button opens a dialog box that includes areas for both components. For more information about this feature, see Logging In and Out of the Repository and ER/Studio TS.
ER/Studio Data Architect now allows association between business terms in Team Server and objects in Data Architect by using the relates to relationship. Objects that support this capability include Entity, Table, Attribute Column, and Domain. For more information about this feature, see the What’s New topic Supports the 'relates to' relationship between Business Terms and Objects.
ER/Studio Data Architect now supports the where clause for SQL Server 2008+ and Azure SQL DB filtered index. For more information about this feature, see Microsoft Access, Azure SQL DB, and SQL Server Index Options.
ER/Studio Data Architect now supports the Columnstore index for SQL Server 2012+. For more information about this feature, see Microsoft Access, Azure SQL DB, and SQL Server Index Options.
The new Spatial tab in the ER/Studio Data Architect Index Editor allows users to configure geo-spatial indexes for SQL Server 2012+ and Azure SQL DB platforms. For more information about this feature, see Spatial tab.
This version of ER/Studio Data Architect allows users to define table and index compression for SQL Server and Azure SQL DB platforms. The Compression option allows you to choose from row or page compression types when using compression and the On Partitions options lets you specify which partitions are affected. For more information about these features, see Microsoft SQL Server Table Storage Options and Microsoft SQL Server Index Storage Options.
The ability for users to model temporal tables for SQL Server 2016 and later is now included in ER/Studio Data Architect. The System Versioning Properties feature allows you to select between anonymous or a named History Table when using temporal tables. For more information about this feature, see Microsoft SQL Server Table Storage Options.
The new Extended Properties tab exists for SQL Server Tables and Columns to manage a list of extended properties. You can add, edit, and delete property values and descriptions. For more information about this feature, see Extended Properties tab Table options and Extended Properties tab Column options.
ER/Studio Data Architect now supports SQL Server 2019 database platform. For more information about supported databases, see Supported Database Platforms.
ER/Studio Data Architect now supports MySQL 8.0 database platform. For more information about supported databases, see Supported Database Platforms.
Users now can use the Output as plain JSON checkbox to remove all MongoDB-specific constructs when generating a database for a MongoDB model. This option removes MongoDb constructs such as ObjectId() and instead a generic JSON is generated. For more information about this feature, see MongoDB JSON Generation.
ER/Studio Data Architect now supports Azure Synapse Analytics. For more information about supported databases, see Supported Database Platforms.
This release of ER/Studio Data Architect add support for Inheritance Relationships for PostgreSQL. The Inherits checkbox in the Properties tab is enabled only for Identifying Relationships. When this option is checked, all other properties on the Properties tab are unavailable (greyed out). For information about creating a new inheritance relationship, see Creating a New Inheritance Relationship.
This version of ER/Studio Data Architect allows you to use TLS between Data Architect and Repository. For more information about this feature, see How to Specify Repository Ports.
ER/Studio now supports the WITH common table expression on Views for SQL Server 2005 and later, Azure SQL DB, and Azure Synapse Analytics. You can use a CTE clause in a CREATE VIEW statement as part of its defining SELECT statement. Note that you can apply multiple CTEs to a view and that CTEs can be recursive. For more information about this feature, see Creating and Editing Database View With (CTE) tab.
Visually analyze and document how data flows through your organization without needing to inspect code. View and print data lineage diagrams from the Data Lineage tab. For more information, see "Documenting Data Extraction, Transformation, and Load" in the User Guide.
Viewer users connect directly to all repository diagrams and named releases. No longer are they reliant on ER/Studio users to get the diagrams and place them on a network drive for them to access. Use Team Server Search criteria to find diagrams in the Repository.
Viewer users now have full access to the data dictionary of ER/Studio diagrams. Viewer users can navigate and open all dictionary object editors to browse critical information like attachment values or domain binding information.
Unlimited viewing of Model objects such as Entities, Attributes, Relationships, Views, schema objects, and others. Viewer users have access to all properties such as storage parameters, the DDL preview, definitions/notes – everything.
The Viewer displays the same sophisticated layout algorithms available in ER/Studio. The layout engines can be used to clean up a model layout prior to printing to make the model more readable.
ER/Studio Viewer now allows the user read-only access to the property editors for all objects on the diagram and in the explorer tree. You'll have complete, detailed model information such as definitions, notes, constraints, dependency and pre/post-SQL, and relationship properties.
A customizable feature that allows the user to instantly obtain information related to the entity/table objects by hovering the cursor over the desired object. The user can customize this view by selecting text from the entity's definition, notes, attributes, keys, color properties, and more. Select "View" from the Main Menu, then select the "Model Help Settings" submenu for the complete list.
Easily browse and find information within the model with a familiar Explorer-type browser. Toggle between Logical and Physical Models, drill down to the attribute level while the application highlights the object on screen for easy identification.
This sizable, positionable window magnifies the view of all objects on the modeling workspace underneath the cursor. This is particularly useful when navigating large models.
Choose the level of information you wish to view within the model as it appears on the workspace. The user can choose to see the model as a series of simple entities and their relationships, can expose all of an entity's attributes, view only the primary keys, and more. In addition, the users can increase or decrease the zoom-level via a readily available toolbar selection.
ER/Studio Viewer allows the user to toggle between any one of the three leading data modeling notations supported by the native ER/Studio Data Architect application: IDEF1X, Information Engineering (IE or 'Crows Foot'), and Filtered IE (hidden foreign keys).
ER/Studio Viewer allows the user to print diagrams. The application has the same level of printing support available in the native ER/Studio application. A full range of printing capabilities is available, including print-to-scale, and more.
Provides the same level of information found in the commercially available version of ER/Studio, including information on the data modeling notations, how to use ER/Studio's advanced graphical features, and more.
ER/Studio features an HTML help facility that takes advantage of the universal search and browsing capabilities of a browser based system.
Important Release Advisory
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 [email protected].
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:
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).
To download evaluations of other IDERA products or to learn more about our company and our products visit us at www.idera.com.