Understanding Complete Compare Differences After Converting Your Models

Transcription

1 Introduction After converting your v diagrams to Release 7 you may want to validate them using Complete Compare. During the comparison, differences may arise, and those differences are usually the result of changes to the internal data structures that store all of the required information about your diagram (the metamodel) and the additional object-properties that become available within r7. The purpose of this technical document is to list all of the known differences that may occur during a Complete Compare, the situations that result in them, and how to filter out those known differences using the option sets provided. Conversion Options. Four situations may result in differences when comparing diagrams converted from v to r7: 1. Convert an AllFusion Manager from v to r7. a) Using AllFusion ERwin Data er v , check the model out of AllFusion Manager v and save that offline as a *.er1 file. b) Convert the v AllFusion Manager to r7. c) Using AllFusion ERwin Data er r7, open the model you checked out in step a from r7 AllFusion Manager. d) Using AllFusion ERwin Data er r7, Complete Compare the model opened in step c with the v model (*.er1) checked out in step a. 2. Open a v diagram (*.er1) using AllFusion ERwin Data er r7 and Save As r7 (*.erwin). Then Complete Compare the r7 model with the original v model. 3. Open a v diagram (*.er1) using AllFusion ERwin Data er r7 and Save As r7 (*.xml). Then open the XML file using r7 and Complete Compare that with the original v model. 4. Open the v diagram (*.er1) using AllFusion ERwin Data er r7 and Save As (*.er1). Then Complete Compare both v models using AllFusion ERwin Data er v The Known Differences. In the table below, we list all of the known differences that may appear when comparing two diagrams. If a difference is due to a generated name or a calculated value, that difference will show in both an r7 and a v Complete Compare. However conversion issues will only show in a v to v Complete Compare. A generated name is a name that does not come from expanding an AllFusion ERwin Data er macro or similar. A calculated value (derived property) is calculated or derived from other properties. A conversion issue is a difference that occurs due to a difference between the v and R7 metamodel. NOTE: A good way to identify all of the generated names and calculated values is to save a model to XML format using r7. While saving the XML file a dialog Save As XML File appears that asks you to select an XML format. Choose the option AllFusion Repository Format that will expand the macros otherwise you will not see any of the calculated values. The calculated values in the XML file show a tag that says Derived="Y". Here is the list of differences that may be expected between converted models and their original diagrams. This is a deprecated reference property from means that is a property no longer used in versions of ERwin later than v :

2 r7 Object r7 Property Differences Seen Attribute PB Edit Style This is a deprecated reference property from The value of the property is ignored when loading a Attribute PB Initial This is a deprecated reference property from The value of the property is ignored when loading a Attribute PB Mask This is a deprecated reference property from The value of the property is ignored when loading a Attribute PB Pattern This is a deprecated reference property from The value of the property is ignored when loading a Attribute Datatype In R7, attributes deriving from User Defined Datatypes (UDDs) cannot have overridden datatypes. If this occurs in a legacy model, the overridden datatypes are removed on conversion, and will show datatype differences after a round-trip through R7 Attribute Logical Datatype In R7, attributes deriving from UDDs cannot have overridden datatypes. If this occurs in a legacy model, the overridden datatypes are removed on conversion, and will show datatype differences after a round-trip through R7 Attribute Storage Object Name Name is generated. Column Name Duplicate column names are not allowed in R7. If a duplicated column name is encountered, the column name is changed. Column [Check Constraint Usage] Name Object generated when loading a model in r7. Column [Check Constraint Usage] Physical Name Object generated when loading a model in r7. Column [Check Constraint Usage] Validation Object generated when loading a model in r7. Column [Check Constraint Usage] Value Object generated when loading a model in r7. Column [Default Constraint Usage] Parent Default Constraint Usage Ref Value missing after saving an R7 model back to.er1. Since Default Constraint Usage objects are created in R7, not having this property does not have any consequences. Column Default Value Default value will be missing on migrated columns when FE scripts generated from an ER1 and ER1ConvertedToR7 are compared. This is because R7 does not automatically migrate default and check constraints via relationships, as is the case in legacy Erwin Column Validation Rule Default value will be missing on migrated columns when FE scripts generated from an ER1 and ER1ConvertedToR7 are compared. This is because R7 does not automatically migrate default and check constraints via relationships, as is the case in legacy Erwin Complete Compare Report Option Set If a Complete Compare Option set was created in R7 and is not created as a logical or physical option set, it is not saved as a option set. Default On save-as ER1 from R7, duplicate default objects are created for every usage of the default in the model (other than on domains). The constraint usage name is saved as the default name. This applies to the non-bind defaults on SQLServer-compatible databases

3 Domain Datatype In R7, domains deriving from UDDs cannot have overridden datatypes. If this occurs in a legacy model, the overridden datatypes are removed on conversion, and will show datatype differences after a round-trip through R7 Domain Logical Datatype In R7, domains deriving from UDDs cannot have overridden datatypes. If this occurs in a legacy model, the overridden datatypes are removed on conversion, and will show datatype differences after a round-trip through R7 Domain Where domains are duplicated 414 CC cannot match Drawing object [Rectangle] Background Color The value of the property is ignored when loading a Drawing object [Rectangle] Background Pattern The value of the property is ignored when loading a Drawing object [Rectangle] Background Style The value of the property is ignored when loading a Drawing object [Rectangle] DO Font The value of the property is ignored when loading a Drawing object [Rectangle] Font Color The value of the property is ignored when loading a Drawing object [Rectangle] Location The value of the property is ignored when loading a Drawing object [Rectangle] Name The value of the property is ignored when loading a Drawing object [Rectangle] Outline Color The value of the property is ignored when loading a Drawing object [Rectangle] Outline Style The value of the property is ignored when loading a Drawing object [Rectangle] Outline Width The value of the property is ignored when loading a Drawing object [Rectangle] Text The value of the property is ignored when loading a Drawing object [Rectangle] Text Adjust On The value of the property is ignored when loading a Drawing object [Rectangle] Text Break On The value of the property is ignored when loading a Drawing object [Rectangle] Text Horiz Align The value of the property is ignored when loading a Drawing object [Rectangle] Text Vertical Align The value of the property is ignored when loading a Drawing Object [Shape] Name Name is generated. Includes rectangles, ellipse, lines, etc. Drawing Object Entity Anchor Point Calculation difference Drawing Object Entity Fixed Size Point Calculation difference Drawing Object Entity Location Calculation difference Drawing Object Child Side Connection Calculation difference Drawing Object Child Side Position Calculation difference Drawing Object Child Side Vebphrase Calculation difference Drawing Object Child Side Vebphrase Calculation difference Coordinates Drawing Object Location Calculation difference Drawing Object Mid Point of Relation Calculation difference

4 rectangle Drawing Object Middle Verb Phrase Calculation difference Offset Drawing Object Parent Side Calculation difference Connection Drawing Object Parent Side Position Calculation difference Drawing Object Parent Side Verb Calculation difference Phrase Drawing Object Parent Side Verb Calculation difference Phrase Coordinates Drawing Object Subtype Symbol Stored as a separate object in R7. Entity DB2 Valid Proc In 414, you can have multiple attachments of validation rules to a single table when the database is DB2/390. In r7, each table can only have one validation rule attached. Only one validation rule will be attached to a r7 table and the remainder of the attachments will be lost. Font A garbage font may come into the r7 model when saved to.erwin. Font Duplicate fonts are removed Index Physical Name Name is generated. Key Group Name Name is generated. The way that the name is generated is different in R4 and R7. R4 uses "Primary Key" and "Foreign Key [X]" while R7 uses "XPK[Entity Name]" and "XIF1[Entity Name]" Many To Many Transform Many To Many Transform objects are not saved from a r7 model to a.er1 file. Only the target objects of the transform gets saved to the.er1 file. Unresolved transforms in the legacy model are not converted, and will be lost in a round-trip through R7 Client Calculation difference Index Name Macro Differ When loading a model in r7. R7 uses %KeyName to map key group name to index name. Logical Notation Differ When loading a model in r7. Schema Gen Options Calculation difference Reports Unique Names The value of the property is ignored when loading a Volumetrics Blob Block Size Volumetrics Blob Factor Volumetrics Bytes Per Char Volumetrics Index Factor Volumetrics Log Percent

5 Understanding Complete Compare Differences After Volumetrics Row Overhead Volumetrics Table Factor Source When saving an r7 model as an r4.er1 file, model sources that are not.er1 files are removed. Object Physical Name White-spaces that preceded names in 414 were considered illegal characters and replaced by the underscore ('_') for all objects whose names were DBMSvalidated. Since white-spaces preceding names is invalid on most databases anyway, R7's approach is to trim these leading spaces. In such cases, conversion differences wrt physical names will be seen Physical Storage Object Name Name is generated. Type, Nullability Non-identifying relationships are converted to identifying on conversion, if all attributes migrating via the relationship are part of the entity's PK. Conversely, identifying relationships are converted to non-identifying if migrating attributes are non-pk Child Delete Trigger Template Ref Child Insert Trigger Template Ref Child Update Trigger Template Ref Parent Delete Trigger Template Ref Parent Insert Trigger Template Ref Parent Update Trigger Template Ref Logical Only, Do Not Generate When a relationship is imported into r7, if Logical Only is set on the relationship, the Do Not Generate property is set on the r7 object instead and the Logical Only property is removed. The Do Not Generate property is also set if the relationship has a parent or child that is a Logical Only entity. When reverting back to r4, the Logical Only property will be set on the relationship if the Do Not Generate property is set. This is done because there is no Do Not Generate property in and this will ensure that the relationship won't get generated in any SQL.

6 StoredDisplayProxyObject Page Grid In r7, page grids settings are stored individually for each diagram (stored display). In r4, the page grid property is set at the model level. If a model is opened in r7, all page grid properties of the stored display proxy objects will be set according to model level page grid in the model. When reverting back to r4, if one stored display in teh r7 model has page grids set to true, then the model level page grid property will be set to true in the r4 model. Subtype Symbol Source of Transform Transform objects are not saved from a r7 model to a.er1 file. Only the target objects of the transform gets saved to the.er1 file. Supertype Subtype Roll Down Supertype Subtype Roll Up Supertype-Subtype Rollup/Rolldown Transform objects are not saved from a r7 model to a.er1 file. Only the target objects of the transform gets saved to the.er1 file. Unresolved transforms in the legacy model are not converted, and will be lost in a round-trip through R7 Supertype-Subtype Rollup/Rolldown Transform objects are not saved from a r7 model to a.er1 file. Only the target objects of the transform gets saved to the.er1 file. Unresolved transforms in the legacy model are not converted, and will be lost in a round-trip through R7 Table Drawing Object Ref Table Index Global Partition Name Differ when loading a Table Index Local Partition Name Differ when loading a Table Partition Description Name Differ when loading a Object UDP Definition In R7, there is a completely separate set of UDP definitions for the logical model and the physical model. In R4, objects type that are common between the two models share a set of UDP definitions. Such objects include, Subject Area, and Stored Display. UDPs for those objects that originated in R4 and are saved to an.er1 file from R7 will be duplicated as one UDP is for the physical model, and the other is for the logical model. UDP Definition Validation Rule Validation Rule Validation Rule For entities and attributes, duplicate UDPs are created for subtype symbols and domains respectively when a R4 model is opened in R7. Additional/duplicate validation rules are showing up. R7 allows naming reference between column and Check Constraint Usage object. In order to preserve these names, we create validation rules and duplicate the values. Duplicate validation rules are renamed these show as differences On save-as ER1 from R7, duplicate validation rules are created for every usage of the rule in the model (other than on domains). The constraint usage name is saved as the validation rule name. This applies to all validation rules targetting databases that do not support validation objects (such as Oracle), and only to check constraints for target databases that do support validation objects (such as SQLServer)

7 View Understanding Complete Compare Differences After Teradata View Locking Clause View Drawing Object Background Color Calculated value View Drawing Object Fixed Size Point Calculation difference View Name Name is generated. Entity Column Order Difference in order due to the different ways physical unification is handled in R4 and R7 Entity Attribute Order Difference in order due to the different ways physical unification is handled in R4 and R7 View View Column Order Difference in order due to the different ways physical unification is handled in R4 and R7 An explanation of some of the differences. Object generated when loading a model in r7 means that difference is a result of a change in the meta model. In some cases, a concept that was represented as a single object in v is not represented as two or more objects in r7. In other cases, the object is new to the R7 meta model. Calculation difference. These are minor positional differences in the diagram. The diagram itself should still look pretty much the same in r7 as it was in v Only one validation rule will be attached to an r7 table and the remainder of the attachments will be lost. In v you had the capability to attach multiple validation rules to a table. In R7, you are limited to one. A garbage font may come into the r7 model when saved to *.erwin. In some v models, some unused fonts were hidden from the user. Since these fonts were not used, they are harmless. As a result, properties that were added in SP3 are ignored and will be lost during the conversion process. If you should Save As an r7 model (*.erwin) to v (*.er1) you will lose the properties specific to SP3 that were not supported in SP2. So saving an r7 model to v is done at the Service Pack 2 level, not at the SP3 level. Filtering Out Known Differences. You can "filter out" the known differences using the Complete Compare Option Sets. Below we describe how that may be done using either r7 or v Using the Complete Compare filter with r7. Attached to this document is an XML file (LP MM Conv Option Set.XML) that contains a customized option set that will filter out most of the known differences during an r7 Complete Compare. The custom option set also works with diagrams stored using AllFusion Manager r7. You do not have to use our custom option set and can use one of your own if you prefer to do so. The custom option set filters out the following differences: A) Line and entity positions due to a bug that existed in v

8 B) Drawing Objects - v did not name drawing objects and r7 does. Since r7 generates the names independently for each model, the names will not match during a Complete Compare. To use the custom option set, first open the models that you want to compare using AllFusion ERwin Data er r7. Then in the Complete Compare dialog choose the link Type Selection and then press the Open button that is next to Option Set. Select the XML file and the settings will change to the selections that will filter out the differences noted above. You may then proceed with your Complete Compare as usual. Using the Complete Compare filter with v This section applies to the situation where you open a v diagram using r7, Save As v (*.er1), and then go to Complete Compare that model with your original v diagram. Unlike r7, AllFusion ERwin Data er does not allow you to transfer option sets from one model to another, so you either have to choose the selections for each diagram you want to compare with or use the ER1 file that is attached to this document. The ER1 file attached to this document (the filter diagram ) contains a custom Option Set that you can use to "filter out" the known differences. Since you can t transfer option sets from one model to another using v , we need to import all of the objects from one of the models we want to compare with into the filter diagram and then use that to complete compare with the other model. Here are the exact steps to perform a Complete Compare between your pre-conversion v diagram and the diagram you saved as v using r7: Complete Compare of a Post Conversion r7 Save As v (*.er1) to a Pre Conversion (*.er1) Physical Level: 1) Combine the Filter.er1 option sets with your r7 Save As (*.er1) model: a) Using AllFusion ERwin Data er r7, open your *.er1 model from your harddrive, network, or AllFusion Manager r7, Save As v (*.er1) file to disk or your network, and then close it. For our purposes, we will refer to that diagram as diagram A. b) Using AllFusion ERwin Data er v , go to the File menu and Open the diagram Filter.er1. Complete Compare this Filter.er1 with diagram A in this way: (i) From the Tools menu, choose Complete Compare to start the Complete Compare Wizard. (ii) Set the following options in the Complete Compare - Set Options dialog: 1. Compare Type: level compare. 2. Compare Current with: ER1 file; click Browse to select diagram A. 3. Sync Action: Update Current. 4. Compare level: Physical Level then Select "Next". (iii) At the Update - Items to Compare dialog click Next. (iv) At the Update - Object Filter Options dialog click Next. (v) At the Update - Other Filter Options dialog click Next. (vi) At the Resolve Differences dialog click Next. (vii) At the message "The import changes you selected will be applied to model: FILTER," click OK After some processing you will now have diagram A s model objects combined with the Option Set in the Filter.er1 file.

9 c) From the File menu choose Save As and save this combined file to "YourFileFiltered.er1" (or some other name). You are now ready to compare this combined model with the original pre-conversion model. 2) Complete Compare the combined YourFileFiltered.er1 with the original pre-conversion version of the model (i) From the Tools menu choose Complete Compare to start the Complete Compare Wizard (ii) Set the following options in the Complete Compare - Set Options dialog: 1. Compare Type: level compare 2. Compare Current with Mart (choose file) or ER1 file (if you have previously saved your pre-conversion model offline). 3. Sync Action: Update Current 4. Compare level: Physical Level then Select "Next". (iii) At the Update - Items to Compare dialog select the Option Set: Default Option Set - Physical2 then click Next. (iv) At the Update - Object Filter Options dialog click Next (v) At the Update - Other Filter Options click Next 2) View or Report differences minus the known differences. At the Update - Resolve Differences dialog you will be able to see any remaining differences between the pre-conversion model and the r7-converted model without any of the known differences. You may view the differences on your screen, Report on any differences, or Cancel. Complete Compare of a Post Conversion r7 Save As v (*.er1) to a Pre Conversion (*.er1) - Logical Level: 1. Combine the Filter.er1 option sets with your r7 Save As (*.er1) model: A. Using AllFusion ERwin Data er r7, open your *.er1 model from your harddrive, network, or AllFusion Manager r7, Save As v (*.er1) file to disk or your network, and then close it. For our purposes, we will refer to that diagram as diagram A. B. Using AllFusion ERwin Data er 4.1.4, go to the File menu and Open the diagram Filter.er1. Complete Compare this Filter.er1 with diagram A in this way: (i) From the Tools menu, choose Complete Compare to start the Complete Compare Wizard. (ii) Set the following options in the Complete Compare - Set Options dialog: 1. Compare Type: level compare. 2. Compare Current with ER1 file; click Browse to select diagram A. 3. Sync Action: Update Current. 4. Compare level: Logical Level hen Select "Next." (iii) At the Update - Items to Compare dialog click Next. (iv) At the Update - Object Filter Options dialog click Next. (v) At the Update - Other Filter Options dialog click Next.

10 (vi) At the Resolve Differences dialog click Next. (vii) At the message "The import changes you selected will be applied to model: FILTER," click OK. After some processing you will now have diagram A s model objects combined with the Option Set in the Filter.er1 file. C. From the File menu choose Save As and save this combined file to "YourFileFiltered.er1" (or some other name). You are now ready to compare this combined model with the original preconversion model. 2. Complete Compare the combined YourFileFiltered.er1 with the original pre-conversion version of the model A. From the Tools menu choose Complete Compare to start the Complete Compare Wizard B. Set the following options in the Complete Compare - Set Options dialog: 1. Compare Type: level compare 2. Compare Current with: Mart (choose file) or ER1 file (if you have previously saved your pre-conversion model offline). 3. Sync Action: Update Current 4. Compare level: Logical Level C. Select "Next." D. At the Update - Items to Compare dialog select the Option Set: Default Option Set - Logical2 then click Next. E. At the Update - Object Filter Options dialog click Next F. At the Update - Other Filter Options click Next 3. View or Report differences minus the known differences. At the Update - Resolve Differences dialog you will be able to see any remaining differences between the pre-conversion model and the r7-converted model without any of the known differences. You may view the differences on your screen, Report on any differences or Cancel. The table below shows additional known differences that may occur when using AllFusion ERwin Data er v to Complete Compare a Post-Conversion r7 Save As v (*.er1) to a Pre-Conversion (*.er1) - Physical Level: r7 Object r7 Property Differences Seen Default Values CURRENT_SQLID & System_Generated In R7, there are different default values so CURRENT_SQLID & System_Generated appear in the R7 converted model but not in the original v *.er1 file. Subtype Name Font Subtype Name Font Inherited Subtype Fill Color Subtype Outline Color Inherited Relation Name Font Exists in the R7 Save As but not in the Original *.er1 Attribute/Column Color

11 Indexes Generate: NO/YES Indexes Physical Name Additional Indexes in the original model Column Comments Distinct Distinct Row View Column Order Blank in R7 model, 0 in the original model Blank in R7 model, 0 in the original model Differences in View column order may occur due to the different ways physical unification is handled in v and R7 Fonts Colors Default Subtype Name Font Default Relation Name Font Default FK Attribute/Column Font Default DO Font Default DO Font Color Default DO Adjust Fit Default DO Horizontal Alignment Default DO Fill Color Default DO Outline Width Default FK Attribute/Column Font Inherited from PK = exists in the R7 model, blank in the original model The table below shows additional known differences that may occur when using AllFusion ERwin Data er v to Complete Compare a Post-Conversion r7 Save As v (*.er1) to a Pre-Conversion (*.er1) - Logical Level: r7 Object r7 Property Differences Seen User Rule Entity Subtype Name Font Entity Subtype Name Font Inherited Was blank in the original model. Appears with values in the R7 model. Did not exist in the diagram. Changed to Arial in the R7 diagram. Was 1 in the 414 diagram, changed to 0 in the R7 diagram. Entity Subtype Fill Color Was RGB(255,255,255) in the 414 diagram. Changed to blank in the R7 diagram. Entity Subtype Outline Color Inherited Was 1 in the 414 diagram, changed to 0 in the R7 diagram.

12 Relation Name Font Relation Name Font Inherited Relation Name Color Relation Color Inherited Attribute Icon Attribute/Column Font Inherited PK Attribute Order Entity Colors Default Subtype Name Font Default Relation Name Font Default FK Attribute/Column Font Was blank in the 414 model. Changed to Arial in the R7 model. Was 1 in the 414 diagram, changed to 0 in the R7 diagram. Was blank in the 414 diagram, changed to RGB(0,0,0) in the R7 diagram. Was 1 in the 414 diagram, changed to 0 in the R7 diagram. Blank in the 414 diagram, Default Number Icon in the r7 diagram 1 in the 414 diagram, 0 in the r7 diagram IDifferences in attribute order may occur due to the different ways unification is handled in v and R7. Shows as blank in 414 but RGB(120,1,11) in r7 Is blank in 414, is Arial in R7 Is blank in 414, is Arial in R7 Is blank in 414, is Arial in R7 Default DO Font Is Arial in 414, is in R7 Conclusion Using Complete Compare is a valid way to compare models converted to r7 with their v originals given that you are also aware of the known differences that may occur. Within this technical document, we have provided a list of the known differences and the situations that result in them. These differences are usually the result of changes to the r7 metamodel and the additional object-properties that become available in r7. Using the option sets and listings of the known differences provided, you may then filter out and recognize most of the known differences.