We just raised a $30M Series A: Read our story

Informatica Enterprise Data Catalog OverviewUNIXBusinessApplication

Informatica Enterprise Data Catalog is #3 ranked solution in top Metadata Management tools. IT Central Station users give Informatica Enterprise Data Catalog an average rating of 6 out of 10. Informatica Enterprise Data Catalog is most commonly compared to AWS Glue:Informatica Enterprise Data Catalog vs AWS Glue. The top industry researching this solution are professionals from a computer software company, accounting for 31% of all views.
What is Informatica Enterprise Data Catalog?

Informatica Enterprise Information Catalog provides a machine-learning-based discovery engine to collect data assets across the enterprise while increasing the understanding of those data assets through a graph-based enterprise information catalog. Powered by Informatica’s unique metadata services engine, Enterprise Information Catalog enables business analysts and data stewards to find all types of data across the enterprise; discover relationships among them; enrich data with business glossary terms and crowdsourced annotations; and understand the provenance, quality, and usage of their data.

Informatica Enterprise Data Catalog was previously known as Informatica EDC, Informatica Enterprise Information Catalog, Enterprise Information Catalog.

Buyer's Guide

Download the Metadata Management Buyer's Guide including reviews and more. Updated: November 2021

Informatica Enterprise Data Catalog Customers

AIA Singapore, Mattel

Informatica Enterprise Data Catalog Video

Informatica Enterprise Data Catalog Reviews

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
Head of Big Data and BI Development at a insurance company with 1,001-5,000 employees
Real User
Top 10Leaderboard
Difficult initial setup and needs better support for data discovery but has an excellent data profiler

Pros and Cons

  • "The way that the solution scans is very useful."
  • "They have to improve their relationship discovery tool. They say that they have AI inside, but this AI did not automatically find relationships or suggested relationships between entities."

What is our primary use case?

We primarily used the solution because we wanted to be aware of metadata management solutions for our Data Lake, in order to manage the assets in the Data Lake and also to manage the ETL or the data ingestion into the Data Lake.

What is most valuable?

The solution has an excellent data profiler.

The way that the solution scans is very useful. 

The discovery worked well for the AS400, which is a very old database.

What needs improvement?

It is not the best solution on the market. 

They don't have a good solution for SSIS scanning, and we don't have the good solution for Microsoft OLAP and Microsoft Tabular. 

Another thing that can be improved is their ability to add custom screens or custom views and manage the custom server and customs views. Currently, it is pretty closed. You cannot add columns to the views, which makes the views very narrow. In order to see data, you have to do a lot of clicks just to get to a particular field.

They have to improve their relationship discovery tool. They say that they have AI inside, but this AI did not automatically find relationships or suggested relationships between entities.

The solution needs better support for data discovery or scans.

For how long have I used the solution?

I've been using the solution for almost two years.

What do I think about the stability of the solution?

The solution isn't too stable. If it crashes, it takes time to boot it back up. It's not as stable as you would expect it to be for this type of solution, which is concerning.

What do I think about the scalability of the solution?

We have five people using the solution as of right now.

Potentially, it is scalable, but is not automatically scalable. If you needed to scale it out, then you would have to add some more nodes in order to be able to support the scalability. As long as you are in the boundaries of your initial setup, then it won't scale. However, if you are exceeding that, then you have to increase memory and data store and maybe even some machines to your cluster in order to support the scalability.

How are customer service and technical support?

Technical support could be improved. From an implementation standpoint, their "customer success" team proved to be unhelpful and did not make what turned out to be a complex set up any easier.

Which solution did I use previously and why did I switch?

We didn't previously use a different solution.

How was the initial setup?

The initial setup was very, very complex. It took us a few months to complete the entire set up. There were a lot of bugs during installation. Also, when we wanted to upgrade from, I believe it was a 10.2.1 to 10.2.2, our production environment was down for a few weeks just because of the update. It was not a straightforward experience.

We had a very complicated environment, so when we worked on this, we also implemented the SDK or the API mechanism that came with the suite. Therefore, there were four people working on the setup for this environment. We also had support from the local integrator and we had a lot of support from some specialists from India.

What about the implementation team?

We had an integrator and some specialists from India assist us in the implementation.

Most of the work we did by ourselves, but we wanted some help from a local integrator. They had a process that they called "customer success". We had a weekly call with them, with the customer success team. The customer success representative brought in the product team for discussions, but it didn't really help us, to be honest.

It requires between one and two people to handle maintenance on the solution currently.

Which other solutions did I evaluate?

We ran a proof of concept or a full selection process and we compared it with some other tools. We selected this tool because it had better support for AS400, which was our main source.

What other advice do I have?

We decided to stop the project because it was too much effort and we couldn't benefit from the solution. We saw that it required a lot of effort just to make it work, so we decided to stop the implementation. We stopped using the solution about two months ago.

If other companies attempt to implement this solution, I would suggest that they try to stick to the features which are there and don't try to extend it because it is not that extendable.

In our case, we needed to get a better contract with the local integrator and make sure that they got paid only upon successful completion of the project. Instead, we paid upfront. I'd advise other companies not to make that same mistake. 

I'd rate the solution five out of ten.

Which deployment model are you using for this solution?

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Product Categories
Metadata Management
Buyer's Guide
Download our free Metadata Management Report and find out what your peers are saying about Informatica, Collibra, Alation, and more!