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 ability to collaborate between different members across the organization is the most valuable feature. It gives us the ability to work on the same model, regardless of where we are physically."
"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"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."
"The most valuable feature is the physical or visual representation of the database, showing the tables, the columns, the foreign keys, and the ability to generate DDL, so you can physically implement databases."
"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."
"We use the macros with naming standards patterns, domains, datatypes, and some common attributes. As far as other automations, a feature of the Bulk Editor is mass updates. When it sees something is nonstandard or inaccurate, it will export the better data out. Then, I can easily see which entities and attributes are not inline or standard. I can easily make changes to what was uploaded to the Bulk Editor. When taking on a new project, it can save you about a half a day on a big project across an entire team."
"The solution's ability to compare and synchronize data sources with data models is fantastic. We use it for that on a regular basis to make sure that changes haven't been made to the database outside of the modeling process. I can take existing databases and reverse engineer them and understand their structure within 15 minutes. If I didn't have Data Modeler it would take hours. It increases our productivity and helps in understanding our legacy application."
"They have a lot of features and the most up-to-date technology integration, which I haven't seen in other products."
"It allows us to have proper documentation in terms of the databases."
"The feature I found valuable in SAP PowerDesigner is extraction. I also like that my company hasn't faced any issues because of the clear documentation about SAP PowerDesigner."
"The initial setup was very easy."
"The solution is a very pragmatic tool. It's quite easy to use."
"Provides the flexibility to create logical and conceptual data models."
"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."
"It offers a lot of features in one solution. You would have to get multiple other products to bundle together all of the capabilities that you get in just this product."
"I do a data-centric design, so for me, the data analysis and design tools are the most valuable features."
"It does not have a cloud application."
"I would like to have more data sources from other, different vendors. In recent years, the vendor has reduced the number of data sources, and I would like to have more data sources for every brand. For example, with Oracle, I would like to have compatibility for many versions, including old ones, not just the most recent."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"I find the UI very clunky and very difficult to use. If I add columns to a table the whole workflow could be so much easier. I get frustrated using it. I've tried other tools. I've tried to get off of erwin a few times. I always come back to it because every tool has its own set of problems, and it seems like if I have to pick my poison, I stay with erwin. But so many things that are clunky with it."
"The interface must be improved."
"The solution's model mark could be better because it crashes sometimes."
"Although Quest Software has made tremendous strides in recent years, they need to evolve more in the big data arena; erwin Data Modeler could use a little more work when it comes to big database designs."
"The navigation is a little bit of a challenge. It's painful. For example, if you've got a view open and you want to try to move from side to side, the standard today is being able to drag and drop left and right. You can't really do that in the model. Moving around the model is painful because it doesn't follow the Windows model today."
"UI could be improved by enabling simpler navigation."
"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."
"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."
"There should be a better usage of current hardware including multicore CPUs, higher resolutions, and multiple displays."
"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."
"One disadvantage of SAP PowerDesigner is that you cannot reverse engineer the ALTER statements, so that's an enhancement or area for improvement I'm looking forward to seeing from the SAP team in the future. That should directly reflect on the physical data models my company builds."
"Not very intuitive or user-friendly."
"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."
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.