I have an ERwin model. This is a local model (i.e., not in Model Manager). I would like to extract the model info into an xls format. Is there a way to do so? Better still, is there a means to reading the ERwin model info via SQL? Thanks.
Data Architect at a financial services firm with 10,001+ employees
Real User
2018-04-25T05:33:15Z
Apr 25, 2018
I have been reported assured that accessing the ERwin model via SQL is possible. However I have not done, nor has my team. Our needs were fully met by the SQL/DDL that was the output from ERwin's forward engineering feature. We found it easy to cast SQL/DDL into XLS or into our meta-data repository.
My suggestion would be:
1. If access via SQL is a must for you, then persevere to find the means.
For example, building add-on capability would require such SQL-level access to the ERwin (meta) model. It is only my guess that ERwin's commercial and therefore understandable desire to protect the IP might be the hindrance. Under NDA and commercial arrangements it ought to be possible to gain access to the ERwin's meta-model.
2. Otherwise you could adopt the approach that we took.
erwin Evolve provides comprehensive graphical support for handling large data models. It offers features such as metadata access, version control, and model comparison, enhancing operational reports and system analytics through its collaborative web-driven design.erwin Evolve facilitates reverse engineering and database integration, fostering collaboration and process exploration through its web interface. Customizable and easy to configure, it supports workflow configuration and...
Sorry the opening line should read "I have been repeatedly assured ...".
I have been reported assured that accessing the ERwin model via SQL is possible. However I have not done, nor has my team. Our needs were fully met by the SQL/DDL that was the output from ERwin's forward engineering feature. We found it easy to cast SQL/DDL into XLS or into our meta-data repository.
My suggestion would be:
1. If access via SQL is a must for you, then persevere to find the means.
For example, building add-on capability would require such SQL-level access to the ERwin (meta) model. It is only my guess that ERwin's commercial and therefore understandable desire to protect the IP might be the hindrance. Under NDA and commercial arrangements it ought to be possible to gain access to the ERwin's meta-model.
2. Otherwise you could adopt the approach that we took.
Regards.