I assess the benefits of IDERA ER_Studio's metadata management for my organization as not as good as Erwin's. Erwin's metadata management is better in how it handles data. There is a lot more user involvement in managing the metadata, primarily because in IDERA ER_Studio, the logical and physical models are separately defined in the same file, so you have to map them every single time. In Erwin, it has a unified structure, so if you make a change in the logical model, it automatically shows up in the physical model. You have to go through a couple of steps in the IDERA model to make sure everything has moved over. While that is not that inconvenient when you are actually doing development, as far as metadata management, that is prone to things getting dropped and missed. The collaboration tools in IDERA ER_Studio are adequate, but I think with Erwin, there is more of an opportunity for things to crash. Changes can be merged in IDERA more fluidly; however, the locking and sharing are a little bit more defined in Erwin. I think the learning curve for Erwin might be easier than IDERA ER_Studio, especially with connecting to different models and systems.
