great questions… Here we go with my best try at answers:

- The reasons for integrating with the metadata partners and the data integration parters was driven specifically by our customers. We have some customers who are interested in using our discovered relationships to populate lineage/metadata repositories for regulatory reporting reasons and we have other customers who want to take the discovered rules to move data using an ETL tool. So integration with ETL or with lineage tools are not more or less usefull than each other, they are just different uses of the same information.

- Why is Exeros making singing vendor metadata bridges rather than integrate with Miti? At the time we did the Informatica integration we did talk to Miti but their solution would not have worked for us because we did not support an XML output. However, we know have both CWM and Exeros XML (which has more information than CWM) so it makes sense to relook at MITI for the reasons you note. Thanks for the suggestion.

it seems as if the blog software is stuck some how on my example. so I am trying one more time and I am taking out the “less than” sign… here goes…

For example, imagine you have one data base with a column called “Age” with the age of drivers ranging from 16 to 102 and in a second database with a column called “YDF” with values of “y” or “n”. As it turns out, YDF stands for “youthful driver flag” and Exeros Discovery will automatically discover that there is a business rule “If Age is LESS THAN 26 then YDF EQUALS “Y” , else “N” “. No other product in the market today can automatically discover this kind of rule or the concatenation, substrings, arithmetic, aggregations or reverse pivots that our Exeros Discovery software finds.

So we are not at all the same as the products you mentioned, which is why we are working with so many of the well known players in the market.

Thanks,

Todd Goldman
VP Marketing and Product Management

For example, imagine you have one data base with a column called “Age” with the age of drivers ranging from 16 to 102 and in a second database with a column called “YDF” with values of “y” or “n”. As it turns out, YDF stands for “youthful driver flag” and Exeros Discovery will automatically discover that there is a business rule “If Age

thanks for mentioning Exeros in your blog and thanks for the complements to our marketing team. However, credit really goes to our CTO and engineering team because what we are doing isn’t just clever marketing, there is specific value our product provides that doesn’t exist in the Business Objects, Informatica, or IBM product lines. That is why we are working with all of these companies.

Exeros Discovery is not a data quality or profiling tool. It is a data relationship discovery tool. What we do is discover business rules and complex transformations BETWEEN data sources. The output of this is then used to populate metadata repositories with cross system relationship information or used to figure out how to relate an MDM system to some downstream applications or how to consolidate data sources when populated an MDM system.

For example, imagine you have one data base with a column called “Age” with the age of drivers ranging from 16 to 102 and in a second database with a column called “YDF” with values of “y” or “n”. As it turns out, YDF stands for “youthful driver flag” and Exeros Discovery will automatically discover that there is a business rule “If Age