ER/Studio Home | ER/Studio Documentation | Embarcadero Technical Support | www.embarcadero.com
Read Me Last Updated: January 7, 2013. Any updates to these Read Me notes will be available at docs.embarcadero.com.
Thank you for using Embarcadero ER/Studio Data Architect, previously known as ER/Studio, the award-winning data modeling application for logical and physical database design and construction. ER/Studio Data Architect's (ER/Studio DA) powerful, multi-level design environment addresses the everyday needs of database administrators, developers and data architects who build and maintain large, complex database applications.
ER/Studio DA's progressive interface and processes have been logically organized to effectively address the ease-of-use issues that have plagued data modeling tools for the past decade. The application facilitates your ability to create, understand and manage the mission-critical database designs within an enterprise. It offers strong logical design capabilities, bidirectional synchronization of logical and physical designs, automatic database construction, accurate reverse engineering of databases, and powerful HTML-based documentation and reporting facilities. Before you use ER/Studio, please read the information below.
See the most recent documentation at Embarcadero's Web site, http://www.embarcadero.com/resources/documentation.html.
WHAT'S NEW
What's New in ER/Studio DA 9.5
Release Notes
Upgrade Instructions
Upgrading ER/Studio Repository
Additional Resources
Embarcadero Technologies Technical Support
What's New
What's New in ER/Studio DA 9.5
The following sections provide a brief overview of the major features of ER/Studio Data Architect 9.5. You can find more in-depth information in the New Features Guide and in the Users Guide.
General Updates
Graphics Improvements
You can now select multiple objects (entities, views, and shapes) and apply a layout command. All relationships, view relationships or lines that belong to the selected objects will be affected by the layout. You can use existing layout commands from the menu and toolbar. If you want to layout the entire submodel, no objects should be selected. For more information, see Partial Layout.
Custom Datatypes
Using the Datatype Mapping Editor, you can now create your own custom datatypes. For more information, see Custom Datatypes.
Universal Naming Utility
From the Search Results window, you can now double-click an entry to gain access to the editor for the selected object editors.
Universal Mappings
Mappings you create for Tables, Attributes, Views and Shapes are now automatically matched when comparing and merging models. In addition, mapping you force in the Compare and Merge Utility can be saved in the target model for use in future compare/merge operations. You can see and edit the mappings you create on the Where Used tab of the object.
New Platform Versions
This release enhances support of the following database platforms through additional version support:
New Platforms
ER/Studio Data Architect now supports this database platform:
New Operating Systems
ER/Studio Data Architect now supports this Operating System:
New DBMS Features
DB2 LUW 9.x
TIMESTAMP datatypes now support generated by default option.
DB2 z/OS
Range-partitioned Universal Tablespaces are now supported
Netezza 6.0
Organizing keys are now supported
Oracle 10g and 11g
Capacity planning of tables can now be based on the average row size.
Teradata 12 and 13
ST_GEOMETRY datatype is now supported.
COLLECT STATISTICS and CHECKSUM clauses are now supported.
PostgreSQL 8.0 and 9.x
Support has been added for uuid, money, xml, and serial datatypes; uuid is mapped to the UNIQUEID logical type; money is mapped to MONEY logical type, xml is mapped to XML logical type; and serial is mapped to SERIAL/INTEGER logical type.
Repository Enhancements
Windows 8
Now supported for ER/Data Architect Repository.
Security Center
To make it easier to handle permissions, group support has been added to the ER/Studio Repository Security Center. Repository administrators can assign roles to the group at repository, project and diagram levels, then simply add or remove users from the group to apply the settings to the users quickly and easily. The Repository administrator can either manually create a group and assign users to it or use and LDAP/Active Directory group and add users to the Repository to a group based on LDAP/Active Directory settings.
Release Notes
Known Issues
ERS-21891 | Partial Layout improperly affects edges that are not between selected nodes. |
ERS-21891 | NSU+UNU: Columns renamed using NSU and UNU are deleted from organizing and distribution keys. |
ERS-22022 | Universal Mappings between objects in the same file do not show up properly in Where Used. |
ERS-22037 | UNIVERSAL_MAPPINGS:Universal Mappings aren't displayed properly in Where Used when matching objects in the same dm1 file. |
ERS-22061 | Cannot launch ER/Studio DA 9.5 after uninstalling ER/Studio DA 9.1.4. The workaround is to perform a repair install. |
ERS-22202 | COMPARE_MERGE: GENERATED BY DEFAULT option does not work correctly in logical to physical compare. |
ERS-22206 | Unmatching objects in the Compare Wizard does not automatically delete mappings between the objects. |
ERS-22230 | UNIVERSAL_MAPPINGS: Problems with Universal Mappings in View Editor Where Used tab./td> |
Bug Fixes
ERS-16901 | When you enter Grid Steps Per Line you now see the specified cell per sub grid. |
ERS-17597 | The Compare and Merge utility no longer drops Stored Procedures as if they were Triggers. |
ERS-18942 | New Domains are now created properly if user doesn't have Update Dictionary Object privileges. |
ERS-19083 | Formatting of the Table Summary page generated by the Reporting tool has been improved. |
ERS-19220 | On the Netezza platform, the Reverse Engineering Wizard no longer incorrectly identifies system objects and normal objects. System and user tables and views are now shown correctly in the wizard. |
ERS-19293 | TS: Alter script generated by the Compare/Merge Utility will not run as generated |
ERS-19308 | The Data Lineage dialog now launches quicker. |
ERS-19310 | Submodel Attachment Synchronization now works across .dm1 files. |
ERS-19658 | TS: DATA_SECURITY - Disable arrow keys when a Security Type is selected. |
ERS-19762 | In the Repository options, the server name field now allows more than 30 characters. If the server name is too long to be displayed in the text box, you can click on the text box to see the full name. |
ERS-19943 | On the Netezza platform, data types are merged correctly with and without the override data type option selected. |
ERS-20026 | Changing the table name within DDL tab page is now effortless. |
ERS-20086 | When moving attributes while the entities are checked in you are prompted to check out the entities before you can complete the move. |
ERS-20389 | The automation interface property, DataMovementRuleLink object now returns overriden text using the read/write ValueOverride property and the read only ValueCurrent property. You can also use the ValueOverride property to change the data movement rule. |
ERS-20396 | When a relationship is moved, the verb phrases now maintain their relative position to the relationship line. |
ERS-20513 | The options to reverse-engineer View and Other Dependencies are now saved in Quicklaunch files. |
ERS-20547 | When comparing a PDM from the tool with a database, the Compare/Merge tool now compares the tablespace of a HASH Partitioned PK index. |
ERS-20585 | TS: SQL_IMPORT: Import SQL fails to handle "CREATE OR REPLACE" and "REPLACE" statements. |
ERS-20670 | TS: COMPARE_MERGE: Phantom columns added to table after merge |
ERS-20843 | On the Oracle platform, the constraint name generated is now no longer than 30 characters. |
ERS-20854 | The Index is now recreated when column part of the index is changed using the Compare/Merge utility. |
ERS-20999 | You can now select and modify a relationship placed on a shape. |
ERS-21052 | On the Netezza platform the DOUBLE and DOUBLE PRECISION datatypes are no longer converted to a CHAR(10) datatype. |
ERS-21053 | TS: TERADATA - Support for TITLE option in Teradata |
ERS-21058 | On the DB2 LUW platform, the Generate By Default option is now available for TIMESTAMP columns. DB2 LUW. |
ERS-21071 | On the Oracle 10g platform, function-based indexes now longer show up as being different between PDM and database is there is no differences. |
ERS-21072 | On the SQL Server 2008 platform, the Identity Property options are now included when generating a Physical Model. |
ERS-21705 | TS: AI - Submodel scroll and zoom API properties do not function correctly or at all |
ERS-21078 | Data Lineage has been improved to prevent data lineage transformations from being connected in two different data lineage streams. |
ERS-21084 | Convert Case Name macro is now working as expected. |
ERS-21094 | TS: Named Release General Info discrepancy |
ERS-21100 | The clustered property is now ignored if the platform doesn't support clustered indexes. |
ERS-21124 | When running ER/Studio as a restricted user, there are no longer problems with upgrading models from earlier versions of ER/Studio DA to more recent versions. The memory leak that caused the problem has been fixed. |
ERS-21125 | The active model is now rendered again after deleting an enterprise dictionary to prevent problems when performing a Save As on a Repository file. |
ERS-21126 | Attributes are no longer removed from entities after canceling a checkout during a drag and drop operation. |
ERS-21131 | Refresh now updates macros renamed or added from the file system folder. |
ERS-21156 | Incorrect error no longer displays when editing recursive relationship where attributes are shared in compound primary key. Only one key needs to be rolenamed. |
ERS-21185 | Changing relationship layout from straight to elbowed no longer causes all verb phrase positions to be reset. |
ERS-21237 | If you try to create in submodel a previous deleted cluster between supertype and subtype, the appropriate message is displayed, "This entity is already a subtype of the selected parent entity". Otherwise, the appropriate message, "This entity is already a member of another subtype cluster" displays. |
ERS-21250 | Rolldowns on non-identifying relationships no longer propagate parent PKs to child PKs. |
ERS-21252 | Propagated keys from "Physical Only" relationships no longer show up in Compare and Merge." |
ERS-21263 | TS: COMPARE - Merging relationships does not include column rolename details. |
ERS-21266 | HTML Report now displays the Constraint Name in the correct location within the diagram image. |
ERS-21270 | TS: Get Named Release performance is slow when there are a large number of named releases for a diagram. |
ERS-21278 | Foreign key FK columns are no longer removed from tables as part of the Repository Add Diagram action. |
ERS-21284 | The automation interface property, DataMovementRuleLink object now returns overriden text using the read/write ValueOverride property and the read only ValueCurrent property. You can also use the ValueOverride property to change the data movement rule. |
ERS-21287 | The "Attribute name" field now has the "Logical Rolename" information for non-keys columns when PM is generated with the "Make Native" option checked and parent entity set as "Logical only." |
ERS-21327 | If a procedure references a view and all tables are removed, the diagram can now be added to the Repository. |
ERS-21330 | Drawing Transformation and Data Stream objects is no longer slow with multiple connected sources. |
ERS-21357 | TS: Problem parsing view with USING |
ERS-21367 | Resolved problem with upgrading the Repository database that required columns and rolenames to be updated right after getting a diagram. |
ERS-21371 | TS: COMPARE - Error comparing SYS.XMLTYPE datatypes. |
ERS-21405 | When checking in a model after modifying a view, a "_1" suffix is no longer added to Views with same name but different schema." |
ERS-21462 | TS: Oracle Synonym Wizard does not have enough space to see the full object name. |
ERS-21488 | Column name and rolename are now set properly after a merge. |
ERS-21497 | TS: PROC_PARSE: Syntax error in stored procedure containing keyword 'sparse' |
ERS-21573 | Resolved intermittent crashing problem while generating HTML reports when there is an Enterprise Data Dictionary in the file. |
ERS-21579 | TS: Metawizard - Unable to import SAP MDM 7.1 XML file. |
ERS-21611 | Setting a new attribute or column name using Attribute.AttributeName or Attribute.ColumnName now perform correctly if the name only differs by case. The Convert Name Case macro now works as expected. |
ERS-21618 | TS: OBJECT_TYPE: Syntax error near "'@someVariableName'" returned on the type validation |
ERS-21637 | TS: VIEWS - Support for the UNIPIVOT function within Views. |
ERS-21659 | TS REVERSE-ENGINEER: Sybase Connection is refused when having the ocs.cfg file |
ERS-21644 | Changes in General tab of the Naming Standards Template Editor are now saved to the Repository. |
ERS-21645 | Changes in General tab of the Naming Standards Template Editor are no longer overwritten when upgrading to the ER/Studio Data Architect 9.x.. |
ERS-21681 | Extra 'r' character is no longer appended to AS in the View validation. |
ERS-21728 | Relationship lines are no longer hidden during image copy and paste when in front of shapes, |
ERS-21729 | TS: ER/Studio crashing after macro execution |
ERS-21733 | Images copied to the clipboard now preserve their shadows, subtype connections, and subtype arrow graphics when pasted into other applications. |
ERS-21734 | TS: Subtypes no longer display correctly - lines do not meet shape |
ERS-21906 | TS: Ability to specify a float type without having to specifying the width. |
ERS-21915 | You can now specify the COMPRESS property for TIMEZONE and VARCHAR columns. |
ERS-21922 | TS: INDEX_EDITOR: Should enforce index name uniqueness at the table level instead of the model level for Teradata |
ERS-21924 | TS: MODEL_OPTIONS: Crash changing model options when focus is on a submodel |
ERS-21928 | Compare/Merge operartion involving denormalizations no longer cause an application crash. |
ERS-21939 | in the Export MetaWizard, the password is no longer displayed in readable text. |
ERS-21936 | TS: REVERSE_ENGINEER: Large view DDL statement truncated after reverse-engineering from Teradata |
ERS-21977 | Resolved error when importing Teradata comments. |
ERS-22056 | TS: METAWIZARD: Crash accessing Export Submodel Metadata on a partial physical diagram |
ERS-22062 | TS: Reverse Engineer - MySQL table name starting with number fails. |
ERS-22080 | TS: COMPARE_WIZARD: Problem matching security objects when comparing models |
ERS-22141 | TS: DDL_GEN: The order of foreign key columns is wrong, referencing wrong columns. |
ERS-22152 | TS: DDL_GEN: [TERADATA 13.10] Generated DROP INDEX statement is syntactically invalid. |
ERS-22214 | TS: REPO_MERGE: Submodel layout changes lost when second user checks in unrelated change |
Upgrade Instructions
Upgrading ER/Studio Data Architect Use the following checklist to ensure ER/Studio Data Architect is correctly upgraded. Upgrade Checklist Important Notes The steps that follow are for ER/Studio Enterprise installations only, which include ER/Studio Repository. Upgrade Instructions Follow the instruction for installing ER/Studio Data Architect, in ER/Studio Quick Start Guide located in the installation Readme directory. If you have an ER/Studio Data Architect installation that does not include ER/Studio Repository, see "Upgrading ER/Studio Data Architect Standard Diagrams".
If you have ER/Studio Enterprise, which includes ER/Studio Repository, see "Upgrading ER/Studio Data Architect Diagrams."
Note: Since the denormalization feature changed in 9.0, any documents containing denormalization mappings will be upgraded to use this feature. Denormalization mappings are now retained with the table data and can be viewed and edited on the Where Used tab of the Table Editor. Denormalization history, including Columns, Indexes, and Relationships of pre-map tables, is no longer retained, so the undo and make permanent functions specifically for denormalizations are no longer available. Denormalization mappings have been worked into the normal undo function of the product allowing them to be undone like other operations. However, the names of the pre-map tables are retained. Retaining only essential pre-map information means that the DM1 file with denormalizations is smaller and therefore opens faster. Upgrading ER/Studio Data Architect Standard Diagrams Note: This procedure is for ER/Studio Data Architect Standard installations only, which do not include the Repository. Once you have installed the new version of ER/Studio Data Architect, from the new version of ER/Studio Data Architect, open each of your old *.dm1 files. ER/Studio Data Architect will convert the files to the new format before opening them. Then save the files with a new name or overwrite the previous version by using the same name. Upgrading ER/Studio Data Architect Diagrams Note: This procedure is for ER/Studio Enterprise installations only, which include ER/Studio Repository. Update your existing diagrams before you check out any diagrams or do any work with the new version of ER/Studio Data Architect. Upgrading diagrams can be time consuming and memory intensive. The number and size of ER/Studio Data Architect diagrams managed in the upgraded Repository will dictate how long the upgrade process takes. This will update your existing diagrams to the latest version. Notes
Upgrading ER/Studio Repository
Use the following checklist to ensure ER/Studio Repository is correctly upgraded.
Upgrade Checklist
Important Notes
Preparing to Upgrade the Repository
Note: This procedure is for ER/Studio Enterprise installations only, which include the Repository. When you upgrade ER/Studio Data Architect you must also upgrade ER/Studio Repository to correspond with the same build date as ER/Studio Data Architect.
The Repository services and your existing database will be upgraded to the current version.
Note: If you are upgrading from a Repository version prior to 4.0, you can delete the C:\Program Files\Embarcadero\Repository\Data directory. This directory is not used with Repository versions 4.0 and later.
Embarcadero Technologies Technical Support
If you have a valid maintenance contract with Embarcadero Technologies, our Support team will assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period.
Evaluators receive free technical support for the term of their evaluation. To download evaluations of Embarcadero Technologies products go to the www.embarcadero.com.
To contact Support, go to Support.