We performed a comparison between erwin Data Modeler by Quest and SAP PowerDesigner based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Architecture Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The logical model gives developers, as well as the data modelers, an understanding of exactly how each object interacts with the others, whether a one-to-many, many-to-many, many-to-one, etc."
"The solution’s code generation ensures accurate engineering of data sources, as there is no development time. Code doesn't even have to be reviewed. We have been using this solution for so long and all the code which has been generated is accurate with the requirements. Once we generate the DDLs out of the erwin tools, the development team does a quick review of the script line by line. They will just be running the script on the database and looking into other requirements, such as the index. So, there is less effort from development side to create tables or build a database."
"erwin has versioning so you can keep versions, over time, of those models and you can compare any version to any version. If you're looking at a specific database and you want to see what changed over time, that's really useful. You can go back to a different version or connect that to your change-control processes so you can see what was released when."
"There is absolutely no problem with the stability."
"The visual data models for helping to overcome data source complexity and enabling understanding and collaboration around maintenance and usage are excellent. A picture speaks 1,000 words. Seeing a picture that shows you how the data relates to each other helps you better understand what the data is and how to use it. Pairing that information with a dictionary, which has the definitions of the tables and columns or the entities and attributes, ensures that the users understand what the data is so that they can use it best and most successfully."
"The fitting model is very intuitive."
"It supports a wide variety of databases, including the latest ones. We have chosen to go for a cloud-based database, and it supports that, which is very useful."
"The product allows us to reuse entities and attributes."
"The most valuable features of SAP PowerDesigner are the creation the flow charts and folders. It is a powerful tool."
"It has helped me to develop the as-is state, design its to-be state, and track the capital investment according to gap analysis."
"I do a data-centric design, so for me, the data analysis and design tools are the most valuable features."
"Has a specific template that's very helpful for importing metadata."
"The most valuable feature is the way you can extend it and customize it. With most modeling tools, you fit your modeling process to fit the tool. In PowerDesigner, you can make the tool fit the way you want to work."
"I've used the reverse engineering feature a lot. I can take a look at the structure of the database and what relationships it has."
"In terms of operational efficiency and cause savings or return on investment, I can say that with SAP PowerDesigner, our company saves a lot of time."
"It can automate many routine tasks and save human resources to focus on real problems."
"The solution's model mark could be better because it crashes sometimes."
"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."
"In terms of improvements, support could have been better in terms of installation, especially of workgroups. We struggled quite a bit to get it up and running. Collaboration could have been better from an installation perspective, but it is trivial as compared to what we use it for. Other than that, I don't have much feedback. It works pretty well, and the fact that we've been using it for more than a decade shows that it is quite solid."
"The erwin ETL functionality has room for improvement when it comes to mapping databases with a classic entity-relationship model to a data warehouse model."
"erwin is not as robust as a data warehousing project I've been on in the past."
"It would be nice to have it on the Linux platform, not just Windows. If they can support Linux, there would be a huge market for it."
"The erwin Data Modeler is quite complex to use."
"The interface must be improved."
"Technical support could be better and more human."
"SAP PowerDesigner could improve by making the repository easier to understand. It is difficult to understand how the repository works because when I used logical models as part of the team, we wanted to use them together and update the older versions of the data model version but it was confusing. The repository needs to be explained."
"The data governance should be improved, like ER/Studio."
"UI could be improved by enabling simpler navigation."
"You have the possibility to complete a connection for abbreviations if you are creating columns or names of the tables. In the Citrix environment, this has been lagging to the point where the PowerDesigner was not usable."
"Regarding improvements, I suggest enhancing the connection between objects in process and data models. It's crucial to define the structure of objects, especially when dealing with standard frameworks like VMM. There should be better visualization of arrows between BPM and data modeling objects, specifying their structure and impact. For future versions, a feature similar to Bizagi, allowing users to see forms or SQL representations of objects, would be valuable for demonstrating and presenting project details to stakeholders."
"The solution is very, very expensive. It would be ideal if it was a more affordable product."
"There are many areas of this solution that needs to be changed."
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while SAP PowerDesigner is ranked 5th in Enterprise Architecture Management with 34 reviews. erwin Data Modeler by Quest is rated 8.6, while SAP PowerDesigner is rated 7.8. The top reviewer of erwin Data Modeler by Quest writes "The product lets users import different types of models, but it is expensive, and the interface must be improved". On the other hand, the top reviewer of SAP PowerDesigner writes "Effective in terms of validating everything, but sometimes they don't allow us some flexibility and GUI could improve". erwin Data Modeler by Quest is most compared with IDERA ER/Studio, Visio, Lucidchart, Sparx Systems Enterprise Architect and AWS Well-Architected Tool, whereas SAP PowerDesigner is most compared with Sparx Systems Enterprise Architect, Visio, IDERA ER/Studio, LeanIX and MEGA HOPEX. See our SAP PowerDesigner vs. erwin Data Modeler by Quest report.
See our list of best Enterprise Architecture Management vendors.
We monitor all Enterprise Architecture Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
15 years ago was the one time I chose to use PowerDesigner over Erwin Data Modeler was for a project where we have hundreds of pl/sql ETL scripts that needed to be run in a specific order for specific tables. PowerDesigner had the ability to store the pl/sql within the data model and prioritize/order the script run sequence. This meant that we could count on PowerDesigner to automatically generate the ddl and pl/sql code in the correct run order, rather than manually maintaining a spreadsheet with the script order and running each script manually, a VERY labor intensive process. I don't know if PowerDesigner still has that capability.
With all of the ways we have to program and perform ETL, Erwin Data Modeler has been my tool of choice for any other project throughout the years. Protecting intellectual property and transparently sharing data model information with other modelers by saving the the models in a centralized location (i.e. Model Mart) is important for any company. Making the data model diagrams transparently accessible via Web Portal is another important step in ensuring both technical and business users understand the structure and relationships of the data contains within a data store. Lastly, making the data model metadata available via the Erwin Data Intelligence Suite enables both technical and business users to completely understand everything about the data and data store: Business Glossary, Reference Data, Governance, Data Quality, Data Mapping, and especially automating data lineage and impact analysis.