RepreZen API Studio vs. Toad Data Point

RepreZen API Studio is well suited for running on two operating systems and the nice UIs are good. But better appearance could improve the UX.

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

• Running on OS X and Windows
• Great performance
• Nice UI and UX

• 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

• 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 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

It's really easy to make APIs via RepreZen API Studio.

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

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