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."We had some data integration projects, where we needed to integrate it for about 100 databases. Doing that manually is crazy; we can't do that. With erwin, it was much easier to identify which tables and columns could be used for the integration. That means a lot in terms of time and effort as well as my image to the customer, because they can see that we are providing value in a very short time."
"It reduces monthly savings by hundreds of thousands of dollars. Think about a company like Costco and all of the points of sale systems in Costco, all of the systems, the applications, but if all the applications in Costco all had their own data model, trying to integrate those, upgrade them and manage their different versions of the same model throughout the store, is an absolute nightmare. It's phenomenally expensive. This helps reduce that cost significantly. I'm talking on the orders of hundreds of thousands of dollars."
"The solution is good for organizing the data and the scripting part is very powerful. It's easy to create technical scripts for models."
"Being able to point it to a database and then pull the metadata is a valuable feature. Another valuable feature is being able to rearrange the model so that we can display it to users. We are able to divide the information into subject areas, and we can divide the data landscape into smaller chunks, which makes it easier to understand. If you had 14 subject areas, 1,000 entities, and 6,000 columns, you can't quite understand it all at once. So, being able to have the same underlying model but only display portions of it at a time is extremely useful."
"What has been useful, I have been able to reverse engineer our existing data models to document explicitly referential integrity relationships, primary/foreign keys in the model, and create ERDs that are subject area-based which our clients can use when working with our databases. The reality is that our databases are not explicitly documented in the DDL with primary/foreign key relationships. You can't look at the DDL and explicitly understand the primary/foreign key relationships that exist between our tables, so the referential integrity is not easily understood. erwin has allowed me to explicitly document that and create ERDs. This has made it easier for our clients to consume our databases for their own purposes."
"We use the Forward and Reverse Engineering tools to help us speed things up and create things that would have to be done otherwise by hand. E.g., getting a database into a data model format or vice versa."
"It provides flexibility with the code. You can change the code as you want. Basically, you can change SQL based on what's best for your project."
"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."
"SAP PowerDesigner is an excellent tool that does what I need it to do. What I like most about it is that it's stable, fast, and easy to understand."
"The most useful feature has been the detailed possibility to model almost anything regarding physical databases."
"The solution is a very pragmatic tool. It's quite easy to use."
"SAP PowerDesigner is fairly stable."
"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."
"The most valuable features of SAP PowerDesigner are the creation the flow charts and folders. It is a powerful tool."
"The most valuable features of the solution are it's built very well, easy to use, and simple to describe freely what is needed in logical and physical data models."
"The initial setup was very easy."
"I would like to see the reporting capabilities be more dynamic and more inclusive of information. The API is very sparsely understood by people across the user community."
"The only real complaint I have is the time it takes to do a database comparison on a large model. If they could speed that up, that would be the only thing I can think of that needs improvement."
"I would like to see more support for working with the big-data world. There are so many new databases evolving and it's very hard for them to keep up with all of the new technologies. It would be good if they were able to dynamically support big-data platforms, other than Hive and Teradata."
"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."
"The report generation has room for improvement. I think it was version 8 where you had to use Crystal Reports, and it was so painful that the company I was with just stayed on version 7 until version 9 came out and they restored the data browser. That's better than it was, but it's still a little cumbersome. For example, you run it in erwin, then export it out to Excel, and then you have to do a lot of cosmetic modification. If you discover that you missed a column, then you would have to rerun the whole thing. Sometimes what you would do is just go ahead and fix it in the report, then you have to remember to go back and fix it in the model. Therefore, I think the report generation still could use some work."
"The erwin Data Modeler is quite complex to use."
"Some Source official systems give us DDLs to work with and they have contents not required to be part of the DDL before we reverse engineer in the erwin DM. Therefore, we manually make changes to those scripts and edit them, then reverse-engineer within the tool. So, it does take some time to edit these DDL scripts generated by the source operational systems. What I would suggest: It would be helpful if there were a place within the erwin tool to import the file and automatically eliminate all the unnecessary lines of code, and just have the clean code built-in to generate the table/data model."
"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."
"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."
"I have found the solution not easy to use. When publishing you have to download the HTML, make adjustments against the updated HTML, convert it to HTML, then finally paste the HTML. There is not an on-the-fly function available to bypass the step-by-step converting process that other solutions have."
"The portal of SAP PowerDesigner could be better. The tool also needs more features and integration with other products, such as Collibra. It would be interesting for SAP PowerDesigner to have more integration."
"The solution is very, very expensive. It would be ideal if it was a more affordable product."
"SAP PowerDesigner can improve the ease of use. It is not the best tool on the market because it is tough to navigate and use. A beginner would not be able to use it well, it requires some experience. If the solution was more user-friendly it would be able to be used by more audiences. I do not think many people are aware of this solution and they should use it."
"The focus is more on mainstream development environments, and I see a lack of focus on the open source world. I think SAP PowerDesigner probably interfaces better with SQL Server and Db2 but not with open source databases like PostgreSQL and MySQL."
"This product does not have a good BPMN Modeler."
"The data governance should be improved, like ER/Studio."
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while SAP PowerDesigner is ranked 4th in Enterprise Architecture Management with 32 reviews. erwin Data Modeler by Quest is rated 8.6, while SAP PowerDesigner is rated 8.0. 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 "Difficult to operate, long process to publish, but scalable". 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.