PowerDesigner allows team collaboration and helps support strong data governance.
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
We use SAP PowerDesigner as our E-R Modeling tool for our application suite. We have twenty-four databases with approximately 3000 tables and 50,000 data elements. We use a repository-based version of the tool and are able to create multiple models that can be used to show various subject areas within the system. We have also taken advantage of customizing the templates to generate objects based on the DDL for the table. PD is an enterprise approved tool and our group has used it since 2001. I personally have used it since 1996.
Pros
- Data modeling
- Maintaining a consistent data dictionary through the use of the repository.
- Custom templates for generating objects off of tables.
Cons
- It took some time to figure out how to leverage the power of the repository. Some better examples in the documentation would have been helpful.
Likelihood to Recommend
SAP PowerDesigner allows our team of data modelers to work and collaborate from a single repository and single data dictionary. This helps enforce consistency as data elements are referenced in other objects. Prior to our use of PD, we might have an element named "ppt" in one table, "participant" in another table and "part" in a third table. By forcing everything to be used from the data dictionary, we avoid these situations because everyone has to go to the dictionary. And we are able to easily do peer reviews on models before they are released because we are collaborating through the use of the repository.