Once we generate the DDLs out of the erwin tools, the development team does a quick review of the script line by line.
#Sap abap vs powerdesigner code#
We have been using this solution for so long and all the code which has been generated is accurate with the requirements. You can go back to a different version or connect that to your change-control processes so you can see what was released when." "The solution’s code generation ensures accurate engineering of data sources, as there is no development time. If you're looking at a specific database and you want to see what changed over time, that's really useful. Those features in erwin are valuable." "erwin has versioning so you can keep versions, over time, of those models and you can compare any version to any version. Visio isn't going to reverse-engineer that for you.
"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." "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.