IBM InfoSphere Information Server vs. Red Hat JBoss Data Virtualization vs. Toad Data Point

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.

Red Hat JBoss Enterprise Data Services is a top choice for JEE applications. Even though lots of documentation is available, it's difficult in terms of usability. If the development is more based on Java applications it is a good choice. It provides better installation and integrations.

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

• 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

• Data source compatibility: since it is Java, it can connect to anything with a JDBC driver.
• Flexibility: you can configure it however you want, we have it configured to use LDAPS for authentication and have all interfaces encrypted, and setting that up was pretty straight forward.

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

• 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

• Pricing
• User Interface

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

• Scale of implementation
• IBM techsupport

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

Support availability and resolution response time make it a better choice.

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

Market value and support extended by Redhat is the winner against Veritas. It has cool features and functionality but still, if your organization is Redhat shop it's better to go for the Jboss option.

Incentivized

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

Incentivized

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

• It has allowed us to start moving applications independent from their underlying data sources, savings us time and limiting cutover effort.

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