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 is used by more than 50,000 professionals in 60+ countries to get big results from their enterprise data initiatives. erwin is the #1 choice in virtually every industry, from government and healthcare to retail and finance.
erwin Modeling provides a collaborative environment to manage enterprise data through an intuitive, graphical interface. With a centralized view of key data definitions, you can leverage information as a strategic asset and more efficiently manage your data resources...
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.