OpenText Magellan BI & Reporting vs. Toad Data Point

iHub is a decent enough environment that it serves our needs. We can have unlimited users and it can tie into AD although we do not use that feature currently. It is a decent place to store all of the reports in one location, even though for us it is not visually appealing to the end users. iHub is not a place where you want to create robust/interactive dashboards for end users to drill through and follow a "story".

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

• It is fairly easy to set the sharing rules for a report/dashboard.
• They have a decent amount of time frame options for setting a schedule to generate a report.
• The support is mostly helpful and timely if you have an issue.

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

• Setting up a "dashboard" is extremely lacking in functionality. The different chart widgets you place on the page do not interact with each other. When you select an item from one do not expect it to highlight or filter another.
• The speed and stability are not great, but maybe that is just our environment not being up to snuff...even though we are above the "recommended" settings.
• The main GUI for a user is TERRIBLE. You log into a File Tree format where you have to navigate folders to reach the correct dashboard. There are ways around this, but it would either require an expensive payment to the Professional Services team to revamp to UI or another option they gave us was to create the "Default Dashboard" and provide that link to users and in that Dashboard, you use a new tab to include the navigation back to the main screen so that at least on the initial load the user is taken to a friendly looking dashboard instead of a file tree.

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

Our instance of iHub does not stack up against the other larger BI tools out today. It is a good place to store reports in a central location that allows users to run very specific reports on demand, but it is not a place I would want to store all of my "dashboards". As far as holding individual reports that are specific to an individual need, it is a great tool. If you want to create a report that will be used as a Template for a Form or a Label, iHub is a good choice to store and schedule the report or call it via API to generate it and return it to your calling app.

Incentivized

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