triggered by the TDM 184.108.40.206 announcement, I installed and tried this new release. I imported a TDM2 XML model (DMX).
For production, we still use the 2.25 version as it supports the SAPdatabase MaxDB natively. I’m still patiently waiting for TDM3 tosupport it too
A) Simple compare
My intention was to find differences between two schemes, as we get the fabulous “ORA-00904 / invalid column name” error without any additional information. I know about Oracle tracing to find the errors, but here I’d like to find the errors using TDM3.
How will I find the missing column(s) if comparing two schemes? I’ve Reverse Engineered both schemes “ZVDC” and “DC25” and using the new Comparator dialog I get too much differences.
Example: the tables ACTIVITY_DEF and KEYFIGURE exist in both schemes.
In the Comparator dialog my result is:
DC25.ACTIVITY_DEF … (not exists)
DC25.KEYFIGURE … (not exists)
(not exists) … ZVDC.ACTIVITY_DEF
(not exists) … ZVDC.KEYFIGURE
So, the tables exist in both schemes. Furthermore they are created using the identical DDL script. Can I switch off the schema name in the Comparator?
In the Settings dialog I deselected the “Tablespaces” option - still the same result.
B) Case Sensitivity
While comparing views, I noticed case sensitivity. In the model, the schema name is in lower case “zvdc”. The reverse engineering reads schema “ZVDC”, so that all views are displayed as different. Can I switch of case sensititvity?
C) Compare with variables e.g. Primary Keys
From the imported model, the primary key name is “_entname__PK” - in the TDM2 it is defined as %entname%_PK (variable with suffix <_PK>). The PK name from Reverse Engineering is for example KEYFIGURE_PK. How to resolve the TDM2 variables during compare?
Thanks in advance for any hints and assistance!