erwin Data Modeler vs. IBM InfoSphere Information Server vs. IBM Rational System Architect Designer

I have had a chance to use few other data modeling tools from Quest and Oracle, but I am most comfortable using erwin Data Modeler. They understand your data modeling needs and have designed the software to give you a feeling of completeness when you are designing a data model.

Incentivized

Information Server is extremely useful to replace manual developments that require a lot of coding effort. It significantly increases the productivity of the initial development and the future maintenance of the processes since it has a visual development environment with self-documentation.

If you need a whole infrastructure and architect view, IBM Rational System Architect is the way to go. If you need a single diagram or your business process is young enough to support hard documenting, you are fine with an open source tool.

Incentivized

• Reverse Engineering: I love the way we can import an SQL file containing schema meta data and generate ER diagram out of it. This is specifically useful if you are implementing erwin Data Modeler for an existing database.
• Forward Engineering: We use this feature very frequently. Where we do database changes in our physical and logical data models and then generate deployment scripts for the changes made.
• Physical vs Logical Models: I like to have my database model split into physical and logical models and at the same time still linked to each other. Any changes you make to logical model or physical model shows up in the other.

Incentivized

• IIS best for ETL ,not ELT , and many and diffrent source systems.
• It also can process big data , unstuctured data
• It is not only DWH , you can use infosphere for analys and see the bigger architecture of your OLTP systems

Incentivized

• MS Office exporting
• UML modeling
• Transformation to code
• A reverse transformation from code
• Integrates with other IBM products

Incentivized

• Cost is the single largest barrier to entry with this tool.
• Would like to see a greater variety of export options available for use outside of the tool, for example as a vector graphic.
• Support has been uneven at times.

Incentivized

• I would be nice to have a new web development environment for DataStage.
• Connectivity Packs such as Pack for SAP Application are a little pricey.
• It is confusing for new developers the possibility of developing jobs using different execution engines such as Parallel or Server.

Incentivized

• Always has a price. And IBM is not cheap
• Sequence diagrams can get messy (still has a good UI)
• Only support few databases as backend repositories like SQL Server and Oracle

Incentivized

• Scale of implementation
• IBM techsupport

Incentivized

I had a lot of experience using erwin Data Modeler for designing data models. I think it's pretty intuitive and easy to use. It has enough features to represent your database requirements in form of a model.

Incentivized

CA customer support and our account manager have been able to support us with any issues that we have had, from managing our serial keys to issues we logged tickets to resolve. There are aspects of key management that have made it difficult over the years but support usually has worked with us.

Incentivized

Not listed, but I've only used alternatives built into something like the Squirrel SQL editor. That one is semi-functional but lacking many features and, in some instances, just plain wrong. The only pro there is that it's freely available and works over ODBC. I've tried some of the other free ones like Creately but didn't have much success.

Incentivized

DataStage is more robust and stable than ODI The ability to perform complex transformations or implement business rules is much more developed in DS

If you have a budget or the need for a complex modeler or need diagram transformation to code or vice-versa, IBM Rational System Architect is the way to go. If you need few diagrams or don't need the complexity or don't have a budget, Bizagi or Star UML get the things done.

Incentivized

• It is difficult to assign a monetary value to it. The initial learning curve was fairly long.
• It allows us to have better support documentation.
• It allows ease of communications between functional units.

Incentivized

• Productivity of the development of integration processes.
• Better documentation and governance.
• Reduce training costs of various technologies.

• Clients like good modeling. A good diagram reduce costs in incidents and doubts of bad interpretations
• Reduce costs of recognition of old software.

Incentivized