Share your experience using Information Builders Data Governance

My use case for erwin Data Modeler is to identify the objects and keep the business details and object details into one pictorial diagram. Whenever a business wants to understand their operations, it is easy to walk through them with the PDF we have generated, which includes the links between the objects and functionality of the business and description of each column with business context. This tool is helpful for storing all this information.

My favorite feature of erwin Data Modeler is that we can export and import tables directly from the databases. It is easy to map from table to table and column to column.

In managing data across different environments, we are not dealing with the data in erwin Data Modeler. We use it to describe the relationships between tables and define how the data flows from one environment to another. For example, if we talk about a customer table, we define how many columns should be there and the data types and characteristics of that particular column and table. While we can store structure information at the mapping level, we are not managing data within this tool.

I would rate the visualization feature in erwin Data Modeler a six out of ten because the visualization is somewhat poor and some of the features are not user-friendly. You need to spend more time to make it a framework. There are areas where erwin Data Modeler can improve, such as scrolling and zooming in and out to see any particular columns. The visualization is average to above average, but not great.

Erwin Data Modeler could improve in areas such as the interface, as there are features like copy and paste, creating duplicates, and the visualization elements and toolbars which feel quite old. The user interface resembles a 1998 Windows structure, so that can be enhanced.

I have experienced issues with stability in erwin Data Modeler because it does not have an auto-save feature. Whenever I do something and it crashes, I have to start from scratch. There is no automation such as in Word or Excel, where documents auto-save, and if something happens, they start from where they got saved. This lack of an auto-save methodology can be improved so that if a system crash occurs, work can be saved and rework can be avoided.

Scalability in erwin Data Modeler is good as it connects with multiple databases to pull existing table structures. I believe we can read the table structure from any type of database.

I have not contacted the technical support or customer support of erwin Data Modeler. Every product I have worked with captures business frameworks and detailed information. We have not encountered situations requiring customer care support. Erwin Data Modeler requirements function at a standard level, and when we seek something higher, we connect with the team for support.

Neutral

The initial deployment of erwin Data Modeler was easy. It is not overly complex. Those who can understand how Windows functions can easily complete the setup.

Regarding pricing, I am unsure what the exact price is for erwin Data Modeler, but I believe it is not useful for an individual. It is more targeted toward an enterprise level since organizations looking to store business information and relationship values may consider the pricing. I have never thought about that because we never tried to buy it. It is typically for those who need this tool on an enterprise level.

I have not used any alternatives to erwin Data Modeler extensively. I have used Data Vault, but it follows a completely different methodology and does not compare to this tool.

I do not see any integration capabilities in erwin Data Modeler with any projects I have worked on. There are no particular environments such as development, testing, and production. Since there is no end product to place in production, we handle only one environment. The main purpose of integration would be if any output criteria exist. However, the output products are essentially for documentation purposes. So far, in the projects I have worked on, there has been no integration involved with this tool. My focus has been on documentation, which is metadata about the business strategy.

I do not recall how long it took to deploy erwin Data Modeler because there is no deployment involved in my projects. As mentioned, there is no end product for development and production activities. We are merely keeping the business information, and the application of this product serves that purpose. The end result is a PDF representing business data flow.

I am a user of erwin Data Modeler, and I do not have any partnership with them. Partnerships typically involve enterprise levels, but I am a customer. Whenever I start working with a client, they show me the tool, and I begin using it. I would rate my overall experience with erwin Data Modeler an eight out of ten.

My major use case for Microsoft Purview Data Lifecycle Management is for the classification of data.

The features I use most frequently are discovery and labeling. I utilize data lineage insights, but that is with another team. The impact of Microsoft Purview Data Lifecycle Management on my unified data catalog has improved a lot. The improvements I see are in the lineage, the discovery, and the labeling. The DLP component has also improved. It is good for data management. In Microsoft Purview Data Lifecycle Management, improved information security metrics include helping us in discovery and labeling of data to create DLP rules around that.

I think labeling could use a lot more AI assistance. AI implementation into labeling would be beneficial.

I have been dealing with Microsoft Purview Data Lifecycle Management for about two years.

The solution is stable, and I do not remember experiencing any glitches or latency.

I would say the solution is easily scalable.

I think the technical support from Microsoft is good.

Positive

I have worked with a product from another vendor called Forcepoint for data management. I see some big differences comparing Microsoft with Forcepoint. I find Microsoft more convenient and more user-friendly. Microsoft is more user-friendly in terms of the UI and the way the workflows and everything are designed.

I think the installation of Microsoft Purview Data Lifecycle Management is pretty straightforward.

In relation to the research I did in the past, I read information about Cisco Duo, Cortex XDR, Palo Alto, Ivanti, and Microsoft, and I do remember that I reviewed many products. I manage these products myself and have experience and a relation to them. I work with all of these products. I have been dealing with Ivanti Neurons for MDM for almost two years, and now I am not using it. I stopped using it two years back. Today, I manage Microsoft InTune, although I am not managing it myself but there is another team that is managing that. I currently look into other products from Microsoft, like Microsoft Purview Data Lifecycle Management and Defender. We already have an E5 license with Microsoft, so if you want feedback or anything, you can just send me the questionnaire on my email, and I will fill that out. I do not work with Microsoft Purview Data Lifecycle Management Privileged Access Management, PAM. I work with Data Lifecycle Management and compliance management. I am currently managing it. I am just a customer. I prefer to keep my company name confidential. I would like to remain anonymous for both my name and my company name. I do not have a couple of more minutes to discuss some other Microsoft stack products. I would like to know if I will get special access for PeerSpot. I gave this review a rating of 10.