Re: Erwin 414 21
Riley Boylan
One of the most compelling use cases for erwin Data Modeler lies in itsconnection to the increasingly important and evolving realm of datagovernance. erwin Data Modeler Workgroup Edition provides a controlledcentral repository of data definitions and visibility into where and howproperly defined data should be used.
So, what I did is I exported the model to an XML file, cleaned it using XSLT. It all looked good till I found a problem with relationships - historically, we do not name our relationships and leave that to erwin, so the names are R_1, R_2, and so on. After opening an XML erwin starts producing duplicate relationship names.
I could fill pages with addition reasons, the up shot is that tweaking exported xml is not a good idea. If you must produce an XML representation of either the data or the ERwin model, use the ERwin API to move information in and out of the ERwin model.
I have not tried editing/cleansing the Erwin generated XML.But, this is how we do it in our organisation :If there is a Erwin (Logical/Physical) model (v1) and it's corresponding physical database is out of sync then we create another copy of Erwin model (v2) by reverse engineering the physical database then we leverage "Complete Compare" option in Erwin tool to compare and sync-up the v2 changes over to v1.Hope this helps.