What could be improved or added to IBM Infosphere Information Analyzer is more connectors. This solution comes in a package with IBM InfoSphere DataStage and is missing a lot of connectors to various, new data sources, so IBM needs to work on that area. Compared with competitors such as Informatica and Alation which acquired other small companies to work on the connectors, IBM has not done any testing and has tried to develop the connectors in-house, but that's taking a lot of time. As a result, my company is unable to connect to a lot of data sources, particularly modern data sources.

View full review »

The interface is not the most friendly. Performance.

There are also these following features - documented in the user guide - but do not work:

1. Global Logical Variables (GLVs)

2. Migrating projects. Neither the internal method (Export/Import) nor the command line interface (CLI) method work 100%. They always error out.

3. When you open a data rule and do no modifications, when you close it, IA asks if you want to save the changes, even if you did not make any. A bit disturbing when you know you did not change anything yet you start to doubt what you think you know.

My wish list for new features:

1. Ability to use functions on data sources. I do not understand how IBM could miss this. Data sources are not visible when coding custom expressions. For example if you have a field called CUSTOMER.ACCOUNT_NUM, you cannot code TRIM(ACCOUNT_NUM). My workaround is to create a variable in the rule definition then bind it in the data rule. Functions can only be applied to variables, not directly to fields. I have a rule where I do things to about 12 fields - concatenate, substring, length, coalesce, etc - and I had to make up 12 lines in the definition that do nothing but refer to these variables. I had to invent a rule so I coded seemingly useless rule conditions like address1 = address1 just so I have a variable for the field I want to code functions for. Huge oversight on the part of IBM.

2. Copy a data rule and modify the copy. Right now only rule definitions can be copied, not data rules. Sometimes I need to create two or more versions of the same rule. IA forces me to generate each of them from scratch. This is annoying when version 2 is only slightly different from version 1. If it took me an hour to code the original, it would take me close to that amount of time to code the new version. If I could copy and modify, the effort would only take maybe 5 minutes.

3. The date of last modification. IA only shows the date of creation which is generally useless. The last modification date is far more important and needs to be available and visible.

4. A file manager, a la Windows Explorer. I may want to see the list of rules and sort them by date of modification.

5. Enhanced dedup on output. Currently, IA can only exclude duplicates based on the entire record. It should allow deduping on a select set of columns.

6. Feature to select one record from multiple matches in a join. For instance, in Oracle SQL, one can FETCH FIRST ROW ONLY or use ROWNUM or TOP 1.

7. Ability to sort the output.

8. New virtual tables take a while to appear. You create one and the list doesn't list the new table. Wait 15 minutes or so and maybe it will be listed. Or log out and log back in. 

View full review »

They have developed a new product called Watson Catalog, an upgrade from IBM Infosphere Information Analyzer. It is a cloud patch for data. The solution is outdated and is not on cloud. In addition, it is client-based, so clients are not enough to use it.

View full review »

Business Rule builder needs to be worked on - if we jointed tables (even if we create virtual tables) from other modular areas the function would time-out. View full review »

The product can be better in the future by improving the following:

1. Make the IA db more visible so that the analyzed result and output of data rule executable can be easily seen by external programs
2. Enhance the integration between DataStage and Information Analyzer. Since v8.7, the Data Rule stage has been introduced which has dramatically enabled and eased the use of Data rules in IA. I would like to see a similar stage or solution that can be useful in terms of data profiling
3. Support more CLIs or extend the existing IAAdmin.sh and IAJob.sh scripts, which could be more flexible for the end users.
4. Provide more log details when running any data profiling or rules from the console directly. As of v9.1, the troubleshooting process is still painful. Developers have to do that from multiple places, either from the underlying DataStage job log or the log files placed in both server and client side.

View full review »

Performance, more analysis, comparing old results, capability of fixing data problems. View full review »