SAP PowerDesigner Reviews

I use it for business analysis to understand my clients' business flows. I use the various tools available in SAP and the conceptual data models to analyze and understand the business flow.

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.

Even with Microsoft database systems, it describes the data perfectly. I can just include a picture of the database model into my design specifications, and developers would be able to understand it perfectly.

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.

I'm an Apple user and not a Microsoft user, so I would love to have SAP PowerDesigner be available on macOS and not just on Microsoft. Right now, I am forced to install parallels and run a virtual machine on my Apple.

Yes, it's stable, and I haven't found any bugs. Provided that my work files are stored in the cloud, I can access all the models from both my laptop and desktop computers without a problem. The way that they've designed access to the models is quite good.

The interface is way better with SAP PowerDesigner. Other solutions are limited in their designs. They simply focus on the database, for example, and not on the different types of models.

I would advise you to just start using SAP PowerDesigner because it's intuitive. You have to be a software engineer if you want to use it; you have to know what you're doing. You can't use it as a casual user. However, the models use standards, so they're not difficult to use once you know what you're doing. If you want to design a database, there are other tools that have similar conventions, but SAP's implementation is intuitive and easy to understand. So, my advice is to just directly use it.

Apart from some improvements needed to integrate better with open source systems, SAP PowerDesigner is an excellent tool. It's very easy to use and is very stable. I would give it a rating of nine on a scale from one to ten.

The solution is useful for data warehousing. I'm a contractor and I work with various companies. Each of them have different versions of the product installed, some on-prem and some in the cloud.

I mostly work on the conceptual and logical side of things, and I enjoy how easy it is to use.

I've tried to use Power Designer to bring in images, which didn't work very well at all.

I think it's probably one of the best solutions, but it is not at all easy to deploy in a big organization. I think it's a problem because of internal processes, and you have to find the right person to help you. SAP as a whole is a very big, complex animal.

I have used this solution on-and-off for 23 years. 

It is a very stable solution, but we have big issues if we try to bring in FSLDM. I'm sure Power Designer can handle it, but I think it drops the links because FSLDM is such a huge model. You can't always trust it because FSLDM was not developed in Power Designer.

I think it's a scalable solution. In one company we have a 38-user license, but that's a very large bank. In another company, there's only one person doing data modeling.

The complexity depends on the client, the firewall, and the company's rules of who can use and view different things. 

The implementation can be done in-house. The time it takes depends on the client. In some instances, it takes quite a while if there are a lot of firewall issues to deal with and the client wants it deployed in the cloud.

I would not recommend this solution to others who are considering it. 

I would rate this solution as an eight out of ten. 

I am a computer designer and I consult to various companies. I use PowerDesigner for my own system modeling, which I then share with engineers and ultimately, the customer.

Examples of the types of modeling I do are insurance billing and banking products.

I do a data-centric design, so for me, the data analysis and design tools are the most valuable features.

The interface is user-friendly. Because of the graphic nature of it, it helps you to be able to manage complicated systems much easier.

Better support for integration with open-source technologies is needed. For example, I try to use open-source databases such as Postgres and MySQL instead of Microsoft, DB2, or Oracle. However, I think it's lacking in capability from the tool to the database.

In the future, I would like to see data manipulation capability where you can actually write SQL queries and manipulate data from directly within the tool.

I have been using SAP PowerDesigner for more than ten years.

PowerDesigner is definitely stable. I have been using it for a long time and I have had no crashes. It just works.

Because SAP is pushing it and they use it as a design tool, I think it's very scalable for collaboration. However, I have no idea in practice because I'm just using it myself.

In the time that I have been using this product, it has never been necessary to contact technical support. I think that the help files, along with what you can find using Google, are explanatory enough.

The two other products that I have used are erwin Data Modeler and Enterprise Architect. I switched because of the scope and the user-friendliness of the tool. PowerDesigner used in conjunction with SQL Server is quite amazing. They work well together.

The initial setup is straightforward. There's nothing complex about it.

It will take some time to teach yourself how to use the product, but the installation is nothing. It's an hour or two to deploy it.

I bought the software outright and do not pay a licensing fee.

I have been looking for a tool to interface seamlessly into an open-source environment, and what I have found to be lacking is a visual database prototype tool. I would like something like, for example, Microsoft SQL Server Management Studio that can access the data instead of just the definitions for it. I am constantly searching for an open-source tool that can do not just modeling, but data manipulations or data definitions in a better way.

I certainly recommend using this product, although it wasn't cheap so cost is a consideration. Price is a complaint that I have for most design tools in the IT world, as most of them are extremely expensive. Corporations and large companies can use them effectively.

For me, the GUI is definitely a pleasure. At the same time, there is a steep learning curve when dealing with bigger and bigger systems. Fortunately, the tool helps with that.

I would rate this solution a seven out of ten.

My primary use case is for data modeling which I then share with our IT department. We are customers of SAP and I'm a data consultant and GDPR.

I really like the import-export feature. It has a specific template that's helpful for importing metadata and that's very helpful for me. 

The tool requires a level of specific knowledge in order to be able to use it so it's not user-friendly at all. It could be more intuitive. I'd like to see better data quality and a dictionary feature in an upcoming release. 

I've been using this solution for six months. 

The solution is stable. 

I don't find this solution to be scalable. 

We're currently looking for external support because SAP are not very proactive when it comes to support.

The initial setup is somewhat complex, although I've seen worse. We work with the vendors to implement this product. Deployment time was around two weeks and the installation took a day. The solution doesn't require any maintenance. We currently have 10 users, and we want to expand that but because the tool is not user-friendly we haven't done that yet. 

SAP is quite expensive, particularly as there are other softwares and tools available that are cheaper or open source, that offer additional features and functionality. With SAP you need to pay extra for some features. 

I'm using SAP PowerDesigner to build and maintain an enterprise-wide relational data model for one of the largest banks in Israel.

As a central DA, I can't do all this work. We distribute our work to different people in different applications, and you have to teach them to use it. SAP PowerDesigner is much easier to use and much easier to teach. We have hundreds of people using SAP PowerDesigner, and you have to teach them, and you have to get them to maintain their own data models.

SAP Powerdesigner helps build proper data models based on the methodology of relational databases, which are now 40 years old. I think the big advantage of Powerdesigner over erwin is its intuitive Microsoft like usability. 

It's much easier to use PowerDesigner than erwin. It's also a cheaper product, and it supports many different relational databases. I think PowerDeisgner is more practical, easier, quicker, and more intuitive. I prefer to use Powerdesigner over erwin for large enterprise applications. 

It's a great tool for documentation. A new data scientist can easily understand the data just by looking at it. Once you are managing your physical data with a logical data model, by looking at this data model, you can understand what it means, the business meaning of the elements which are maintained by the relational database.

Connectivity can be improved because it's not very good. I would expect data catalog types of products to connect to the database, the repository of PowerDesigner, and get the metadata out more easily. 

I think as a company, once Sybase purchased SAP PowerDesigner, SAP's investment decreased. I think the number of new features and the product's development is much slower than before.

SAP PowerDesigner is a stable solution. I would say the quality of the software is good. No issues, visibility is very high, and almost no problems.

We didn't have any problems with scalability. We maintain hundreds of data models in the repository of PowerDesigner, and we are maintaining many versions in each model, sometimes maybe even ten. Sometimes even over a hundred different versions in one model, and we still didn't have any problems.

I think technical support is okay, but it could be better. As they are in France, it's a little difficult to reach them. But it's not much of a problem. For instance, if you need to resolve an issue, you have to provide them with the data model. You have to send them the data model as a problem. To do this with a bank's data model, you need to go through security, and you need to get all the approvals. This part is a huge problem. It's a huge headache, and it usually takes time. It would help if technical support is handled differently and made more accessible. 

I worked with erwin for maybe a year or two. Then we switched to SAP PowerDesigner because of the quality of the product and the price. The cost of the product is cheaper, and the bank was very sensitive to the price. I am happy with the switch to PowerDesigner.

The initial set up of SAP PowerDesigner was okay. But it really depends. For example, the initial setup for a startup would be an easy task. If it's a bank, you can't install it by yourself.
In my experience, it took months to set up and deploy SAP PowerDesigner for one of my banking clients. 

SAP PowerDesigner is cheaper than eriwin.

Before choosing SAP PowerDesigner, we actually evaluated erwin.

I would highly recommend this product to be used in each and every application system where you have to design a relational database. It doesn't matter which relational database as you can use it for MSSQL, Oracle, Postgres.

There are over 50 or 60 different tools like SAP PowerDesigner, but most of them are limited to maintaining a few relational databases like Oracle or MSSQL. But PowerDesigner, as well as erwin can be sued with many different relational databases. This makes it easy to switch and maintain the logical level and then create the DDL for Oracle, MSSQL, MySQL, for DB2, or DB2W.

I am using just part of SAP PowerDesigner as a tool. This is because it offers some additional capabilities, like business engineering. Other additional capabilities that I never used because there were additional tools for that.

Whether we use Powerdesigner or some other different tool, it's impossible to build an enterprise data model for big application systems. For example, a CIF covering the count and the post.

If it's loans, once we have a database with over ten entities, it's very hard to do it manually. You have to work with a tool to create a proper data model, and then a proper database with properly defined entities, primary keys, relationships, and foreign keys. You must have a tool. It's impossible to do it manually.

Once such a data model is created, it becomes the source. When trying to understand the beats revolving around magnetic media, you don't have to use the relational data model and the logical data model to understand the data. Once you understand the data, you know the application system. The data is basically a PowerDesigner. The main usage is to design and maintain the data model, the logical data model, and the physical data model.

The physical data model is achieved by pushing a button, and the tools will automatically create the DDL. You would just have to implement it as it is. You don't have to write the DDL manually. The business understanding and the business requirements are translated into the physical design one by one. The implementation is according to the business requirement, as a business understanding of the system.

On a scale from one to ten, I would give SAP PowerDesigner a nine.

I'm an IT architect. I make use of this particular tool end-to-end, especially when I design objects. I also can immediately create the frameworks in PowerBuilder.

In just one click, I can create everything that I want.

I can download the solution right onto my PC.

It's a fantastic tool. It offers lots of flexibility. It saves companies pain and it keeps everything consistent. Whatever the idea was that started at the business level can go down to the database level.

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.

The one issue I've found goes a long way back, especially from version 6.0 onward. In 6.0 there was a fantastic modeling functionality called "Process Analysis Modeling." It was very simple and very straightforward, yet it covered practically all of the three or four important components, which the software should have.

Later, that capability was taken out of PowerDesigner. It got lost somewhere. Yet it was something that was very, very nice to have. SAP, they missed it somehow. Maybe it was removed in error? If they could bring it back, that would be amazing. 

When we had done some of the model icons to other models attached business process modeling, was far easier. The functionality has gone away. 

The solution is very, very expensive. It would be ideal if it was a more affordable product.

I've been using PowerDesigner intermittently, not continuously. I have been using a few other CASE tools as well. In my estimation, I've been using this one since 1994.

The solution is quite stable. We haven't had any issues in that regard.

The solution is based on a RDBMS database, a proper or relational database. It is a one to multi-person version. Any number of people can work simultaneously on it. They actually can buy the license for their own computer, that's all. Therefore, it can scale easily across teams. You just need to license.

I have a team of about ten people and we all use it. We're a small consultancy firm. Everyone uses it.

We will continue to use the solution and increase it as required in the future.

We don't need to purchase technical support per se. If there is any emergency bug fix, it's called UBS. They would send it to us, especially if we signed a maintenance contract with them. if you don't have a maintenance contract, you can just ask for the UBS. 

If our suppliers want us to use other tools, we of course will, however, we've been using this solution since 1994. I do not recall if we used anything before that, or what it might have been.

The initial setup is very straightforward. It's not complex at all. You just install it. You just click on the install button and go ahead and install everything. 

It will also ask if I want a backend repository database. If you say yes, then they will install the database. It is called a Sybase SQL Anyware. Now it is owned by SAP. I don't know exactly what they call it - maybe SAP SQL Anyware or Sybase SQL Anyware. 

In the end, it doesn't take more than five or ten minutes. it's very quick and efficient.

There was no need for any type of consultant or integrator to assist me in the deployment. It's a very simple process.

The solution requires a license for each user. If you want to add another user, you just buy another license. It's pretty straightforward. 

It's an expensive product.

I'm not using the latest version of the solution, I'm using the one that came out before version 16.

When we go to specific clients if they would like us to define it or some other product, what we do is we model whatever things that they want, inside those particular tools. Some of the tools don't have the entire modeling capability that PowerDesigner offers.

If a company has a team of people or even one single consultant who has the capability to design business architecture, software architecture, database architecture, or infrastructure architecture, they should go for this particular product. None of the other products offer all of these capabilities in one tool.

This is especially true when you design on one model. The architects creating them can pull into the next model - whatever they want to create. For example, if I'm designing a business process diagram, we will be able to capture some data architecture. When we reach the data architecture part of it, all the data items, whatever they already created in the business architecture, can be pulled. It automatically creates the database from the ER diagram.

I'd rate the solution nine out of ten overall.

My primary use case for this solution is to design databases, but I have also used it to design processes.

I also know how to add new features and program using the API. We added some new features to PowerDesigner about five years ago.

The most valuable feature is that we can convert CDM (Conceptual Data Model) to PDM (Physical Data Model), and then prepare an SQL statement to be executed.

It has a powerful engineering feature where if you change the data on a secure server then it will change it in PowerDesigner, too.

This solution has good tools for big data, where you can manage large and complex databases. By comparison, tools such as Enterprise Architect and Visio have problems with big databases.

This product does not have a good BPMN Modeler. Also, the simulations for BPMN modelers are not integrated well enough. If we want this functionality then we have to use another program. Compare this to Visual Paradigm, where we do have a good simulation for the BPMN modeler. 

It is a very stable solution, which is one of the advantages of using PowerDesigner, especially in big databases.

I have not had to speak with technical support for this solution. 

The setup of this solution is easy, but using it is rather complex.

Everywhere that I have used this solution, it was installed by somebody else such as a consultant. However, the installation was easy.

I would rate this solution a nine out of ten.

We were reverse-engineering several databases and doing comparisons.

The most valuable feature is that it is a very fast reverse engineering process. It does a very expansive comparison. 

In terms of improvement, the pricing is a bit high. 

I didn't investigate whether we could run business process simulations like you can do with erwin's process modeling tool. I know you can do process modeling in PowerDesigner. I just don't know if you could run simulations of the process.

I used SAP PowerDesigner for a year. 

It is very stable. 

It didn't seem to really need much extendability. For our features, it covered everything out of the box.

There was only one user for this solution, a data architect. 

We did not require any staff for the deployment or maintenance.

I did not use technical support.

Before PowerDesigner we were using IDERA and erwin. PowerDesigner was better than IDERA, but it's obviously a lot more expensive, so IDERA could be a better value.

With PowerDesigner, I had the whole studio. I had the business process solution. With IDERA there are separate downloads and everything so I only used the data modeling studio.

The initial setup was straightforward. It took around one hour. 

I did the deployment myself. 

If you have the money for it, buy it. If you were budgeted, it would be a worthwhile investment.

I would rate PowerDesigner an eight out of ten. It is very complete and robust. If you're an SAP shop, without question you'd want to use it because you can generate your ETL code as well. That also separates conceptual, logical, and physical modeling really well. I don't know if it's as complete though as erwin's solution. But erwin's solution is evolving and getting better. PowerDesigner has some room to improve, but it's still pretty solid.