erwin Data Modeler vs. Toad Data Point

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

Appropriate for general querying and some DBA work. It's the universal least-offensive solution for most environments - not best of breed, but not subject to unusual/extensive requirements. It just works. On the other hand, some functionality (e.g. data import/export, snippets) are perfunctory and minimal and seem to be either difficult or impossible to automate. If you need to streamline those operations, you'll be forced to rely on third-party solutions that mostly work on top of (instead of with) TOAD.

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

• Export data into excel.
• Export data into excel using a pivot table functionality.
• Navigation between windows is intuitive and easy to understand.
• Good for SQL novices and experts alike.

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

• The workflow is a relatively new feature. Quest is adding additional functionality and the workflows are useful now.
• Would be nice if the 'Automate' feature was a bit easier to use.
• Would be nice if some of the SQL Editor features in the traditional interface worked better in the new workflow interface (although, these are being fixed with each release).
• Would be nice if there were fewer releases.

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

I find Toad Data Point easy to use for both the novice and the experienced business analyst. If all you desire is to access data and create spreadsheets...this is a snap. Toad Data Point actually has cool data analysis features built into it. The newer workflow interface makes automating steps a snap

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

Although Toad and UltraEdit are both great products, from an SQL standpoint Toad is a much better editor and troubleshooter.

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

• It is the least common denominator - not particularly optimized for our environment or workflows.
• Hangs or slowdowns add anywhere from 5% - 7% for projects utilizing large/complicated data setts. (This could be due to other IT-imposed constraints and not entirely due to TOAD.)
• Trying to perform some operations requires reading documentation and experimenting in order to figure out the TOAD-specific approaches and commands.
• It just works (when we understand it). Updates don't break things and things don't suddenly start behaving differently. Best of all, we don't mysteriously lose functionality.

Incentivized