When you don’t know a huge database, inherit it, and don’t have access, the end user does not want to explore the DBMS using the DBMS tools. ERwin could show what is in the Oracle db so the user can see it, and if erwin has a problem with that class of object(s), please tell the end user about it before reverse engineering and taking a very long time to do so.
Please add smart functionality that would perform a mini-analysis prior to a reverse engineer.
1. List all the object names in each category in a tree-like structure for exploring them beforehand.
2. Tell the end user whether or not erwin believes it can reverse engineer that category of objects or not based on erwin reverse engineer rules (e.g. if the materialized view columns are referring to a different schema and cannot be REd, or REd in a reasonable time frame or only a few may be REd out of the many, please advise the user to check off and skip that category of objects as that could cause unusual delays in the RE).
Please sign in to leave a comment.