erwin Data Modeler Reviews

My main use case for erwin Data Modeler is to design the tables after getting the requirements from the business, as per the company requirement. I also use it sometimes for reverse engineering, providing the DDLs and data dictionary to the DBAs once the physical and logical model is created.

I use erwin Data Modeler every day. I work as a data modeler in my company, so when there is a new project, there is a new requirement for a table, or for existing tables we have to add new columns or something. I use erwin Data Modeler all the time.

Sometimes for the data governance project, data stewards ask us for the data dictionary, and we have a report in erwin Data Modeler. These are pre-built reports, and we can provide the data dictionary where we can provide the column definitions as well as the data types per table, so that is very useful and handy.

erwin Data Modeler has positively impacted our organization significantly since it has been in our organization since the beginning, even before I joined, and I find it is very useful, so we rely on this tool.

Regarding specific outcomes or benefits I have seen from using erwin Data Modeler, it helps a lot for finding out or designing the tables, if an existing table exists, or how it can relate between the existing tables before we finalize a new table.

erwin Data Modeler helps improve my data governance frameworks. As I mentioned earlier, getting the data dictionary report from erwin Data Modeler is quite easy, and we can use that data dictionary report directly in our data governance, IBM Knowledge Catalog.

erwin Data Modeler is helping to ensure my data is AI-ready and reliable by getting the proper data dictionary from erwin Data Modeler for all the tables, which helps in the data governance project.

It is quite helpful to assess the role of erwin Data Modeler in strategic decision-making within my organization.

I find the best features of erwin Data Modeler are the relationship diagrams to explain the primary key, foreign key, as well as the indexes. The logical model for providing to the business is very useful, and I like the reverse engineering feature of erwin Data Modeler where with existing tables, you can reverse engineer and find the relationships between the tables. That is very useful, and also, at any point in time, if you need the data dictionary for any table, it is very handy.

Regarding the relationship diagrams and reverse engineering features, they help me in my daily work by allowing me to first get the DDL and then do the reverse engineering to find out if there is any relationship in our legacy system at Honda, the mainframe, where we did not follow the standards. I usually give the entity diagram to the requester.

It is quite easy to create the entity relationship diagram, the logical as well as physical, using erwin Data Modeler.

erwin Data Modeler is quite effective in managing data across different environments such as traditional, NoSQL, big data, and cloud platforms. We currently have the DB2 database, SQL Server, and the cloud as well, and we use erwin Data Modeler for all three.

I have not found anything specific that frustrates me about erwin Data Modeler, but for the federation, they can make it a little better. For designing the federated objects, I find it is a bit rigid. I give eight out of ten because I still have to explore this tool, and as I previously mentioned, for the federated objects, I find it is not flexible. There are a lot more things they can improve on it.

I have been using erwin Data Modeler for the last three years plus.

erwin Data Modeler is very stable.

I would give erwin Data Modeler's scalability a nine out of ten.

The customer support for erwin Data Modeler is very good. They are very responsive, and if we had any issues with the upgrade from a licensing point of view, the replies are very quick, and they are very helpful. I would rate the customer support for erwin Data Modeler a ten out of ten.

We did not previously use a different solution.

I have seen a return on investment from using erwin Data Modeler, as it is very time-saving and requires fewer employees needed. We have only three people using erwin Data Modeler, and we can work very well, even with three people.

I rate erwin Data Modeler an eight out of ten.

Regarding erwin Data Modeler's AI capabilities, I have not explored much about the security point of view, but for data governance, I find it is very helpful for getting the data dictionary report. I have not explored the AI capability of erwin Data Modeler in terms of its accuracy and reliability of output. We have not explored the integration capabilities of erwin Data Modeler in connecting with other tools like erwin Data Intelligence or enterprise architecture tools.

I would recommend erwin Data Modeler to others looking into using it.

When I first started using erwin Data Modeler, there was a particular project that really made me realize its value, especially how I rely on the visualization and engineering features for challenges that would have been tough to handle without it.

For my main use case, erwin Data Modeler fits into my workflow by greatly enhancing our data management processes.

Data models and their metadata play a crucial role in my AI or analytics initiatives, facilitating better insights and decision-making.

erwin Data Modeler has positively impacted my organization by offering specific outcomes and improvements that I have noticed in the process.

Regarding metrics, the improvement brought by erwin Data Modeler is significant: we saved a lot of time on database model updates, reducing the effort by approximately 60 to 70%, and observed fewer schema-related errors.

erwin Data Modeler helps improve data governance frameworks for my organization by ensuring consistent data management across different platforms.

erwin Data Modeler's best features include those that stand out the most for me, particularly in terms of visualization and seamless integrations.

Model comparison and synchronization is a feature of erwin Data Modeler that I use regularly, and it has saved me from major issues or mistakes.

There are additional features of erwin Data Modeler that are beneficial to my workflow.

Regarding erwin Data Modeler's governance and security, I believe it provides solid frameworks to address our organizational needs.

When it comes to erwin Data Modeler's accuracy and reliability of output, I believe it performs exceptionally well.

Creating visual representations of data structures using erwin Data Modeler's enterprise-grade visualization feature involves clear steps that I can explain.

erwin Data Modeler is very effective in managing data across different environments including traditional databases, NoSQL, big data, and cloud platforms.

Integration capabilities of erwin Data Modeler, especially in connecting with erwin Data Intelligence and enterprise architecture tools, play a major role in its efficiency.

erwin Data Modeler ensures our data is AI ready and reliable by implementing structured data management practices.

Transition between legacy systems and modern platforms using erwin Data Modeler is quite seamless, which is highly beneficial for our operations.

erwin Data Modeler can be improved in areas where I think it could perform better, and I appreciate the opportunity to provide these insights.

There are certainly areas where I think erwin Data Modeler could be improved, and there are features I wish worked better or features I would like to see.

I would like to add more about needed improvements, particularly regarding better integration with cloud platforms such as Snowflake, Databricks, and Azure.

I believe I have covered everything majorly needed and primarily focused on regarding improvements needed.

I have been using erwin Data Modeler for more than four years since we started using it.

erwin Data Modeler is deployed in my organization as a traditional desktop-based application, while I have used the public cloud, specifically AWS for centralized access.

Amazon AWS is used as my cloud provider for the deployment of erwin Data Modeler.

My advice for others looking into using erwin Data Modeler is to embrace its full potential and leverage its features effectively.

I would rate erwin Data Modeler a 9 out of 10 because, while erwin Data Modeler is excellent, there are just a few areas holding it back from a perfect score.

My main use case for erwin Data Modeler is to prepare the conceptual, logical, and physical data model for data warehouse or the latest advanced data analytics platform.

To give you a quick, specific example of how I use erwin Data Modeler for creating those conceptual, logical, and physical data models, I basically use it to do the reverse engineering from the source system to understand the existing source system structure, and then I create the conceptual high-level model.

In the current beverage business, for one example, I took nine source systems for planning, mainly the planning data, so I created the first conceptual model, then reviewed it with the concerned stakeholders, and then created the logical model derived from the reference from the source system, and then created a physical model specifically for the database.

To add to my main use case about how I work with erwin Data Modeler, I also do forward engineering to create the structure in the database, and I generate reports for sharing with the data engineering team.

erwin Data Modeler has positively impacted my organization by helping to define models visually so that stakeholders can see them and understand whether the relationships among those entities are defined properly or not.

The data engineering team refers to understand the relationships as well as how the data should be populated, and that's how it's helping the entire organization.

erwin Data Modeler also helps to create artifacts in terms of the data model side for reuse perspective.

Definitely, I can share specific outcomes or metrics that show how erwin Data Modeler has made things better for my organization; it actually reduced the time, helps to deliver projects smoothly, and does not hang or become disrupted from other tools.

So definitely, it speeds up the process for delivery.

Regarding erwin Data Modeler's AI capabilities and its governance and security, I think it definitely helps us define the governance and security.

However, from my experience, I have seen that organizations use different tools for governance and security.

So it's not directly impacting the organization, but it definitely helps.

erwin Data Modeler helps improve data governance frameworks because it provides the artifact for the data model file, like a conceptual, logical, and physical model, connected to the database through different tools, not directly from erwin Data Modeler.

In terms of strategic decision-making within my organization, erwin Data Modeler helps by providing insights into how much effort is required in the beginning.

It definitely helps, but along with other tools also involved in that.

In my opinion, the best features that erwin Data Modeler offers include a very simplified user interface and a very smooth experience in terms of creating tables or entities or structure, and it also provides the lineage.

The process of creating visual representations of data structures using erwin Data Modeler's enterprise-grade visualization feature involves creating subject area perspectives and then integrating those subject areas.

erwin Data Modeler is effective in managing data across different environments such as traditional, NoSQL, big data, and cloud platforms, as it provides great coverage in terms of all those systems.

The transition between legacy systems and modern platforms using erwin Data Modeler is seamless, as it supports both platforms, helping in terms of migrating the data from legacy to the cloud.

One of the things that can improve erwin Data Modeler nowadays is its integration with cloud platforms, as people expect more about automation.

erwin Data Modeler has the experience in terms of the enterprise data models, and people are expecting that if I do reverse engineering from the source system, at least it will give 70% to 80% automation to create the data model.

On top of that, they can have human intervention to redefine or refine the model.

I feel that erwin Data Modeler should include AI integration in the tool in the current landscape.

About the accuracy and reliability of erwin Data Modeler's output, we can't fully rely on the generated model from the AI, but with human intervention, we can refine and at least get some reference from the AI-generated model which helps to speed up the process.

I have been using erwin Data Modeler for around eight years.

erwin Data Modeler is stable.

erwin Data Modeler's scalability is good, as it has features in terms of scalability and allows users to be added without disruption.

For the viewer's perspective, you can easily add users, and it does not create any disruption.

Customer support for erwin Data Modeler is satisfactory.

On a scale of one to ten, I would rate the customer support a nine.

I previously used a different solution including ER/Studio or PowerDesigner because it depends on the organization's decision regarding the tools they want to use.

As a consultant, I use whatever tool the organization has decided to deliver.

Before choosing erwin Data Modeler, we evaluated other options, considering price, experience, comfort, and the benefits we would get from the tool.

Thus, we used those metrics before deciding on the tool.

I would rate erwin Data Modeler an eight out of ten.

I chose eight out of ten for erwin Data Modeler because of its smooth user interface and interconnection between models, and I'm not giving it a ten because I haven't used the latest version and I'm unsure if it has AI integration.

My overall review rating for erwin Data Modeler is eight.

As a data modeler of one medium size Bank in Mozambique, I use the solution to respond to main requirements and I am responsible for building our data warehouse, so I need to use this tool to design the data models, logic, and physical data models.

I use this tool to integrate DDLs into a repository for the Mart server, utilizing it to integrate data from one source to another, while erwin Data Modeler is primarily for creating the models themselves. For ETLs that load data, I use Talend Open Source.

In my organization, I work within a group that involves two or three people using erwin Data Modeler, while the our mother company located in South Africa has more than 20 users.

erwin Data Modeler's best features include its ease of documentation, for example, data lineage, which is easy to document in the tool, and the ability to generate scripts, alter scripts, and create scripts. I find it easy to compare two models if I want to verify that the model I designed matches the model implemented in the database. The comparison between models and data lineage documentation make it a good tool.

Migrating DDLs using erwin Data Modeler is easy because I just connect to the database and generate the data model from what is already implemented, making the process straightforward.

By not having to depend on data modeling teams to send DDLs, if I have a database with 50 tables, using the tool, it takes less than three minutes to view the entire database structure, relationships, primary keys, and field types, whereas building it manually could take days or weeks, so the tool significantly improves this task.

erwin Data Modeler's ability to generate database code from a model for a wide array of data sources saves time in development, as utilizing the solution allows me to accomplish tasks in minutes compared to the extended time required for manual processes.

Regarding code generation, the functionality is well-organized, generating simple, easy-to-interpret code that ensures accurate engineering of data sources.

On data governance, while I do not explore this subject deeply, I have tried some features, such as defining organization-specific naming rules for fields, allowing me to control naming conventions using erwin Data Modeler, which includes functionality to check if the fields follow predefined rules.

While I do not have knowledge about pricing for erwin Data Modeler, I think it could improve by having a feature that allows the publishing of models, similar to how Power BI allows for dashboard publishing for different users within an organization, not just data modelers.

I have been using erwin Data Modeler for two and a half years.

I would rate the stability of erwin Data Modeler as an 8, considering I have not experienced significant downtime, bugs, or glitches.

erwin Data Modeler is scalable. I would rate its scalability as an 8.

I have not required technical support for the past two years because I have been able to accomplish everything I need, so I cannot comment on it.

Negative

In my experience, having used only two tools, including erwin Data Modeler and a tool named Design, I find erwin Data Modeler to be superior due to its greater functionalities, ranking it among the top three best solutions for data modeling.

The transition between legacy systems and modern platforms using erwin Data Modeler is seamless as long as I have the appropriate connector for the legacy system, making integration consistent regardless of system type.

I would recommend erwin Data Modeler to other users because it is one of the best tools on the market, effectively covering about 90% of data modeling needs.

The importance of DevOps GitHub integration lies in the tools facilitating script generation to design physical tables; however, it is crucial to understand SQL to address potential errors, which means the tools improve development time but I still need to know what I am doing.

erwin Data Modeler does not validate data; it focuses on validating the model I build, meaning the rules used to create the model are validated, but for data validation, other tools are necessary, as the primary purpose of erwin Data Modeler is to build models: conceptual, logic, and physical.

I would rate the solution as an eight.

My primary use case for erwin Data Modeler is to model entity-relationship diagrams for databases.

Recently, the software factory, which is the team I work on, was developing a system called School Management, and as responsible for the construction, maintenance, and development of the database, I used erwin Data Modeler to design the entire structure of tables and relationships for this database.

erwin Data Modeler basically helps in the conceptual stage of database design, where we project the entire structure visually, making it easier for us to arrange the tables and create them according to business rules. Subsequently, erwin Data Modeler generates a SQL script that I can easily copy, insert into the real database, and execute so that it creates my database.

erwin Data Modeler helps improve the data governance frameworks in my organization. As I mentioned previously, we use this tool to create all the documentation and entity-relationship diagrams for the databases we use in our organization.

I consider erwin Data Modeler a very useful tool, especially for data teams and especially for new people or those without much knowledge.

Approximately, my team currently takes one to two days at most to create a complete model in erwin Data Modeler, depending on the database size and the usage and business requirements.

A very useful functionality that erwin Data Modeler offers is reverse engineering, where I can take a database that is already created and connect erwin Data Modeler to that database. From that database, it generates the entity-relationship diagram. Another very important functionality is that I can create a script from erwin Data Modeler. I can also choose which objects from that database I want to be included in the script, such as views, tables, relationships, functions, triggers, and procedures, and this helps a lot.

The experience I had using the reverse engineering functionality in migrations or upgrades of legacy systems was very good. By doing this reverse engineering, I can have good documentation of the databases and also version those databases. Sometimes there is a database where we do not have documentation, and then we need to evolve that database to create some new tables. For this, I need to bring that database into erwin Data Modeler so I can draw the structures, since it would be very difficult and impractical to create this from scratch. By connecting erwin Data Modeler to the database, I can do this reverse engineering, which already gives me the entity-relationship of the database in its current state. After that, I can create an initial version, and from there, with other tools like Git, I can create various versions and keep this updated. This way we have the entire lineage and history of changes within the database, which is also very good for audits, to know the entire development flow of the database over time.

I would say that the process of creating visual representations of data structures using erwin Data Modeler's enterprise visualization resource is very intuitive and easy to use. I do not have many points of improvement to add regarding this functionality.

I have only used erwin Data Modeler for SQL database structures so far. I have not used it for other types of NoSQL databases yet, therefore, I cannot comment on those other types of databases. For SQL databases, it is a very useful and complete tool.

I consider erwin Data Modeler to be an excellent tool for those who are beginning. One point of improvement would be to use some plugin or connection with artificial intelligence, because nowadays, many IT systems and tools also use artificial intelligence functionalities to facilitate our development. I think this is a very useful capability.

I chose the rating of seven because it is a very useful tool, but it has some limitations. One of these limitations is that, at least in the version I use—I do not know if newer versions have this—the version I use does not have an AI chat.

The version of erwin Data Modeler that I use does not have artificial intelligence functionalities.

For now, I do not have additional suggestions to improve erwin Data Modeler beyond those I have already mentioned.

I believe that erwin Data Modeler is a tool—at least in the version I use—that does not have so much compatibility and connectivity with other tools. It is a somewhat closed tool where you basically have to work only with it. I also had some difficulties exporting and generating PDFs of the diagrams, and it presented some errors. This is a limitation—I do not know if it is a limitation of the tool or if it is actually a restriction due to licenses—that ends up making this integration a bit difficult. However, regarding connectivity with other tools, I think erwin Data Modeler is a bit limited.

I have been using erwin Data Modeler for one year.

erwin Data Modeler is quite stable.

Until now, I have not had problems related to the scalability of erwin Data Modeler, also because I used it in projects that were not so large and with few users using the tool simultaneously. However, I believe it will serve well when there is a greater scalability requirement.

So far, I have not needed to use erwin Data Modeler's customer support.

I used a free data modeling tool before, but it was a bit more limited and did not have direct connectivity with, for example, the SQL engine that I used—or use—which is SQL Server. erwin Data Modeler has this compatibility, so I can connect directly to my database using a login and password that exist in my database. From there I can do reverse engineering. Therefore, it has much more compatibility and many more functionalities. In fact, there are some functionalities that I have not yet used, but I believe they are very useful and that I can possibly use them in the future.

erwin Data Modeler is implemented in my organization as a local license installed on a local server.

I cannot measure this or give a concrete number on return on investment using erwin Data Modeler. However, I can say that the databases that were created using erwin Data Modeler were very productive. It would be impractical and very time-consuming to create these databases directly in a database engine. Using erwin Data Modeler, it is much easier for us to visualize things before we actually implement them within the database instance. It is possible to create and make changes until the final structure is ready. Only then can we safely execute this script and create the database. Without the tool, we would do this directly in the database, and it would take a lot of time and probably involve a lot of rework.

I did not have contact with the costs and licensing part of erwin Data Modeler. From the moment I started using it until today, the license had already been purchased, and I did not have any involvement with that commercial side until now.

I did not evaluate other options before choosing erwin Data Modeler. This tool was already implemented before I joined the company. Therefore, it is the tool that they officially use. For now, it meets my needs very well, and also, because of the license, it is the tool being used.

erwin Data Modeler is an excellent tool. I rate erwin Data Modeler as seven on a scale of one to ten. I think the security and governance of erwin Data Modeler's artificial intelligence functionalities are adequate.

My use cases for erwin Data Modeler involved being responsible for every subject of the bank for most of the years. It was about a data warehouse covering all the businesses and all the business subjects of the bank, from the customer to different accounts and beyond. This big data warehouse was designed to let users use it to make BI and reporting. I was responsible for the modeling and participated in writing the standard rules so that the model would be consistent. Strictly speaking, for most of the years, I was also the only modeler besides being responsible for the overall data modeling function. In the last year, 2023, they attempted to use erwin Data Modeler as a centralized enterprise version, allowing other people to model single parts and single subjects of the model, but this solution did not have much success because each modeler decided they could do whatever they wanted, and the initiative ended that way.

I have only had experience with an entity relationship model using erwin Data Modeler. I have never had experience with NoSQL or other structures. I did not know that erwin Data Modeler could model things different from entity-relationship models. Can it do that?

Regarding whether erwin Data Modeler helps to improve data governance frameworks, the environment I used to work in did not have an official data governance office at that time. Now I know that it does, but it did not then. However, the job was effectively a data governance job. I can see that erwin Data Modeler is a good tool to have a global view of the different subjects in a big company such as Sanpaolo Bank. A data governance office can definitely use erwin Data Modeler to govern the data environment in a big company like that.

What I like the most about erwin Data Modeler is that I think it is the best tool for data modeling. You can use it as a standalone application, and it is good for that purpose. If you use it as an enterprise version, it is good as well. It is very easy to model a simple one, but as you go to a more complex model, you can do it step-by-step and never lose the view of the big picture. erwin Data Modeler is very well conceived as a data modeling tool.

The visualization feature of erwin Data Modeler was good in my opinion, and there were no problems. Sometimes you had to modify the shape of the table by hand to show everything correctly, but that was because the model was complex. Everything was manageable quite easily. My opinion is based on all the versions I used, so I do not know how it is now.

I dislike that it was a matter of some years ago, so I do not remember any feature that would be not in the modeling, but in the documentation. After modeling, they could have done something better to have reports about the model itself, not about the data, but about the model, which would be useful for a data governance environment. There are many ways to extract reports, but they are very technical and not business-oriented. Even if a model is business-oriented and modeled with business metadata, if I do not put business metadata in the model, the reports will never be business-oriented. I think that this aspect could have been developed further.

I have been using erwin Data Modeler for many years at Sanpaolo Bank, an Italian bank, and I have been the manager of data modeling for the bank, even though I was an external consultant rather than an employee. I served as a manager from 2009 up to 2020 and as a single sector subject modeler up to 2023.

I have seen some lagging, crashing, downtime, or instability in erwin Data Modeler. In the enterprise version, even though I was the only modeler so there was no problem of concurrency, I sometimes experienced crashes, but I am not sure it was because of the tool. It may have been because of network or other issues.

I did not have problems about the scalability of erwin Data Modeler. The job was always the same, but if you mean that the model was growing and growing, then in the last years it was a huge model with many subject areas and especially some tables were linked in different subject areas. It was not a simple model at all. We could manage it always, so if you mean this with scalability, the tool handled a growing model with no problems.

I do not think I have ever contacted the technical support or customer support of Quest or about erwin Data Modeler.

I have never used anything similar to erwin Data Modeler in terms of serious tools. Sometimes I used SQL Server Modeler, but it was not comparable. I do not know how it is nowadays.

The initial deployment of erwin Data Modeler for a new client, as I remember, was easy. There was no problem. I was only a colleague of the people who installed it, but I observed that the initial deployment was not an issue at all.

I have no idea about the pricing of erwin Data Modeler because I have always used the enterprise models delivered by the company I worked with.

The maintenance of erwin Data Modeler did not require any maintenance from me. We worked for some time with a release which was not the last one. As far as I remember, we had problems once, but because the bank forgot to upgrade on time. It was one of the few situations in which the missed upgrade gave problems. Otherwise, we could work one release late with no problems.

I have never tried integrating erwin Data Modeler with Data Intelligence or other enterprise architecture tools.

I rate erwin Data Modeler an eight out of ten for everything overall. As I have experienced it, I have little experience with other modelers, so I can rate it an eight. I do not give it a ten because that would not be honest. An eight is a very good rating, and I say this considering that I have not seen other data modelers of this magnitude.

I was using erwin Data Modeler in my company to create tables, columns, and structures in SQL.

erwin Data Modeler is well organized, and the screen layout is intuitive. The overall positive impact and measurable benefit I experienced from working with it is that controlling the new tables or relations that we were adding was clearly better. The view looked better in erwin Data Modeler than creating them directly in SQL, and this was more controlled than it could be if we created something directly in SQL.

I would like to see improvements in other aspects of the data modeler apart from the errors with the databases. The time that it took to download the new XML was considerable, and if this could be faster, that would be beneficial, though I am not certain if this is related to erwin Data Modeler or our server.

What I did not like was that sometimes while I was creating relations, I was not getting errors. The errors only appeared when I tried to upload the model into a new database, which took a lot of time because I was creating a model, reproducing XML, and then trying to add the XML in the database. At that moment, I was getting the errors, so this cost us a lot of time sometimes.

I have been working with erwin Data Modeler for around two to three years.

I personally have not had any crashes, downtimes, or performance issues with it.

I do not think there are scalability issues. As far as I can recall, if the things I mentioned before could have progressed, it would be better, but I cannot speak to other aspects. Some months have passed since I have not worked with it, so I cannot say with certainty.

Regarding erwin Data Modeler technical support and customer service teams, the experience could have been better. Sometimes I was asking questions and receiving repetitive questions from the team. They were responding to my questions with another question, so I lost a lot of time on some things that I remember we were asking about, and they were not really fast. This could be a better performance.

I have not used any different products of the same kind prior to adopting erwin Data Modeler. The other solutions I have used were only directly on SQL, so I have not used another data modeler program.

Regarding the initial setup process, the experience with the deployment aspect was not complex. I can say it is a friendly application, and you can learn it really fast. It is very friendly. When I started at the beginning, a colleague who was senior taught me, as I was a junior at that time, and I learned it really fast. I can say it is very friendly.

I did not evaluate any other options or solutions available in the market. The company decided to go with erwin Data Modeler, so I cannot speak to alternatives.

I would recommend erwin Data Modeler as a product and solution if companies want to have more control over the new things that they want to add in a database. However, I will not recommend it if they want to save money and create everything in SQL, as there are benefits, but you can also do it without erwin Data Modeler. I have no idea regarding missing features in erwin Data Modeler that I would like to see included in the future, and I have no idea about any advice or recommendation that I would share with other organizations considering erwin Data Modeler. My overall review rating for erwin Data Modeler is seven.

My main use case for erwin Data Modeler is migration, and it is easy to navigate. We can navigate easily, add primary keys, and constraints without difficulty. I can create historical tables easily with that.

Recently, we have two projects, and we are migrating from one project to another. For that reason, we used erwin Data Modeler to copy those tables, extracted the code particularly to SQL scripts, and ran it in SSMS, SQL Server Management Studio, where the tables got copied, and we imported data from the previous project to the current project.

That is the main thing regarding my use case. We also use erwin Data Modeler for relations, such as one-to-one, one-to-many, and many-to-one relationships, as well as for table creations like star schema and Snowflake schema.

erwin Data Modeler has positively impacted my organization because it is easy to use. Doing migrations manually takes more time, but using erwin Data Modeler makes it a very easy task for us to import those tables and extract those codes.

I estimate that erwin Data Modeler saves our team a significant amount of time, with a large project possibly taking three to four months to migrate manually, but we completed everything within one and a half months, using about forty-five days including an extra fifteen days to check all the test cases.

erwin Data Modeler helps improve data governance frameworks by providing end-to-end descriptions, ensuring no leakage of data from one organization to another, making it useful for governance frameworks for my organization.

erwin Data Modeler plays a role in strategic decision-making within my organization by making things easier and taking less time.

In my experience, the best features that erwin Data Modeler offers are its ease of use for anyone, even newcomers, to navigate easily through the application. I suggest everyone use this application as it is very easy and clear.

The specific features inside erwin Data Modeler that make it user-friendly for me are its tools for migration, making it easy to connect the database from the previous project and easily import and extract codes.

Additionally, we have a great feature with automatic saving, which helps a lot.

Concerning erwin Data Modeler's AI capabilities, its governance and security are good, as we work for bank organizations and chose erwin Data Modeler due to the trust, ensuring no leakage of data.

The accuracy and reliability of the output from erwin Data Modeler are good.

I have not noticed any issues with the outputs from erwin Data Modeler except for the slowness. Everything else is good, and the data comes very clearly.

The process of creating visual representations of data structures using erwin Data Modeler's enterprise-grade visualization feature involves easy fact table creations, such as star schema and Snowflake schema, along with having arrows for relationships, making visualization straightforward.

erwin Data Modeler is effective in managing data across different environments as we mostly used it for migration. While we have not used it for big data or cloud, it is easy to manage data across different environments and manipulate it as needed.

Regarding improvements, I have noticed some slowness in erwin Data Modeler, and if it could be made faster, that would be great.

While saving work, it takes more time, which I encountered as a challenge, so improving that would be beneficial.

I have been using erwin Data Modeler for three point eight years.

erwin Data Modeler is stable in my experience.

In terms of scalability, erwin Data Modeler is good.

The customer support for erwin Data Modeler is very good. I have experienced quick responses to queries. I would rate customer support around a ten.

This is the first solution I have used, so I did not use a different solution before erwin Data Modeler.

I have seen a return on investment.

The pricing, setup cost, and licensing for erwin Data Modeler are taken care of by our leads, and as users, we find it easy to use, with the price not being a big deal.

I have not evaluated other options before choosing erwin Data Modeler. It was suggested to me as secure and the best for our organization, which is why we trusted it.

I would rate erwin Data Modeler an eight out of ten. I am decreasing two points because of the slowness, but everything else is good and top-notch. I chose eight specifically because I felt I was working faster with this application. If it was faster, it would be better.

I have not used the integration capabilities of erwin Data Modeler to connect with erwin Data Intelligence and Enterprise Architecture tools.

My advice for others looking into using erwin Data Modeler is that it is an easy application, cost-effective, and there is good support, making it great for newcomers. My overall rating for erwin Data Modeler is eight out of ten.

My main use case for erwin Data Modeler is to implement a single data architecture design department so everyone is using erwin Data Modeler for their data models to be a transactional application or a data repository. Everyone in the company and every project is using it for future implementations, modifications, new projects, enhancements, migrations, and everything.

I have more to add about my main use case and other recent projects where erwin Data Modeler played a key role, as it is a very good tool for data modeling and to control the different data models. At Nissan, there are several applications and different types of applications, and with erwin Data Modeler, the company is able to centralize and have a single language for data modeling and data architecture.

erwin Data Modeler's best feature that stands out for me is the Data Mart portal.

Before Mart Portal, we used to have a repository with shared folders, but now with Mart Portal, everyone is contributing and collaborating using erwin Data Modeler, so it is used as a development repository. This is one example of how erwin Data Modeler and Mart Portal are helping in daily work.

Another feature that stands out for me is the ability to compare data models, which is a good feature because you can compare data models between different database engines. It is also very useful to automate some tasks, such as the ability to import several columns or to translate from logical model to physical model.

erwin Data Modeler has positively impacted my organization by allowing us to implement the data architecture with the data strategy about six to eight years ago, since it allowed us to have a single language and implement new Nissan standards, naming conventions, constraints, and features. It also allowed us to reduce time and cost on generating data models and DDLs, as everything is centralized and everyone interested in accessing that in the organization can do so, allowing us to obtain information from data models and generate reports for some business areas.

Regarding improvements, the first thing I would mention is that every release has some issues, some of which are related to current functionalities, which means they often seem not very well tested or affected in the development process of the new version, leading to issues until that is released. Additionally, some important features such as importing from flat files took a lot of time or several releases to be addressed, and new functionalities for databases sometimes also take a long time. The tool is not too intuitive and you often have to keep searching until you find the option, so making the tool more intuitive is something that could be improved.

erwin Data Modeler needs to enhance the AI capabilities and integrate them with erwin Data Modeler functionalities, as more work is needed there.

The accuracy and reliability of output regarding erwin Data Modeler's AI capabilities also need enhancement, as it is a good start but not very useful in daily work, leading us to see more value in keeping the current erwin Data Modeler with the old options instead of using the new AI functionality.

I have been using erwin Data Modeler for six years.

While I do not have any exact amount, I can say it has helped to reduce the time that developers, designers, and even some domain data architects spent on their tasks by around thirty to fifty percent.

My advice for others looking into using erwin Data Modeler is to understand the functionality and their needs. When they start using erwin Data Modeler, they should find the value for their needs instead of just implementing it without prior knowledge. It is preferable to know the tool's capabilities and go from there. I have given this review a rating of eight out of ten.

erwin Data Modeler helps improve data governance frameworks to some extent. The solution manages metadata in a way that contributes to improving data governance. erwin Data Modeler can support a small team of DBAs in enhancing collaboration among business, IT, and data teams.

The most valuable feature in erwin Data Modeler is the ER diagram. The process of creating visual representations of data structures using erwin Data Modeler is quite good. erwin Data Modeler can connect to most databases, which is acceptable. The solution is more effective in managing data across traditional databases than in managing data across different environments such as traditional, NoSQL, big data, and cloud platforms. I appreciate that erwin Data Modeler is AI-ready, which ensures my data is AI-ready and reliable.

erwin Data Modeler can improve more on the big data and real-time side, specifically with big data and real-time data streams.

The product has been stable and works adequately so far.

Currently, approximately 20 people are using the product.

I would rate technical support at a six. There is room for improvement when it comes to resolution time.

Before using erwin Data Modeler, I also worked with freeware.

My experience with the deployment was quite straightforward. The setup took a few days in my case. I am currently using the on-premises model.

I have not seen a return on investment yet.

I have been satisfied thus far, and I think the pricing is reasonable. I purchased erwin Data Modeler directly from the vendor, Quest.

erwin Data Modeler is the best option on the market at the moment for team-wide use. I would rate erwin Data Modeler overall a seven.