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 most valuable features are being able to visualize the data in the diagrams and transform those diagrams into physical database deployments. These features help, specifically, to integrate the data. When the source data is accumulated and modeled, the target model is in erwin and it helps resolve the data integration patterns that are required to map the data to accommodate a model."
"When you're getting down to the database level, where you're building a design and you're creating DDL out of it, or you're going in the other direction where you're reaching into system catalogs and bringing things back, that starts to really require specialization. Visio isn't going to reverse-engineer that for you. Those features in erwin are valuable."
"The product allows us to reuse entities and attributes."
"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."
"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."
"We find that its ability to generate database code from a model for a wide array of data sources cuts development time. The ability to create one model in your design phase and then have it generate DDL code for Oracle or Teradata, or whichever environment you need is really nice. It's not only nice but it also saves man-hours of time. You would have to take your design and just type in manually. It has to take days off out of the work."
"It's a safeguard for me because I'm always concerned that somebody is free handing it and will forget a key coming from the parent. The migrating keys are a great feature. Identifying relationships, non-identifying relationships, and being visually right there to understand the differences are great features. erwin is key to being able to visually understand whatever the customer is requesting. They'll give you words on a paper, but once they can actually view it as a picture, it really comes to life. The data comes to life to where they understand exactly what they're asking for."
"It is a scalable solution...The technical support team is fine."
"The most valuable features of SAP PowerDesigner are the creation the flow charts and folders. It is a powerful tool."
"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 physical database model is definitely the most valuable feature because it describes normalization exactly the way you understand the data, and it deploys it perfectly with open source systems."
"I like the property sheet capability and the user-defined attributes that you can set up."
"SAP PowerDesigner is fairly stable."
"Has a specific template that's very helpful for importing metadata."
"The most valuable feature is that it is a very fast reverse engineering process. It does a very expansive comparison."
"I do a data-centric design, so for me, the data analysis and design tools are the most valuable features."
"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 interface must be improved."
"The solution's reporting side needs to be improved."
"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."
"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."
"There is a lack of local support in the China region."
"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."
"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."
"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."
"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."
"It would be helpful if there were glossary, catalog and governance tools. It would help make it a true end-to-end product."
"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."
"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."
"UI could be improved by enabling simpler navigation."
"Pricing for small consultancies needs improvement. They sustain prices to competing tools. The competing tools tend to do special offers. PowerDesigner SAP doesn't pay much attention to the pricing of it and there are no special offers."
"I've tried to use Power Designer to bring in images, which didn't work very well at all."
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 33 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.