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.
SAP PowerDesigner and erwin Data Modeler compete in the field of data modeling, each offering distinct advantages. SAP PowerDesigner holds the upper hand in detailed data architecture modeling, while erwin Data Modeler shines in usability and integration, appealing to organizations prioritizing rapid and user-friendly deployment.Features: SAP PowerDesigner is known for its comprehensive enterprise data architecture capabilities, complex database support, and extensive customization options....
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.
Hi @George McGeachie, @Carel Van Der Merwe, @Peter Vlekkekn, @Tracy Hautenen Kriel , @Sharon Allen, @Jose Luis Leon and @Pam Rivera,
Can you please share your professional opinion/experience with our community?