Tuesday 16 October 2018

erwin Data Modeler




  • easy to use
         
  • native support for many databases
         CA ERwin Data Modeler (or ERwin for short) is a data modeling and database design tool that is used to create conceptual, logical, and physical data models. ERwin can create the actual database from the physical model, and create different physical implementations from a single logical model. ERwin can also reverse-engineer existing databases into a data model diagram. ERwin works with many database management systems (DBMS). Outputs from the tool include entity-relationship (ER) diagrams and standard or custom reports on all objects in the design (tables, fields, relationships).

      Access, IBM DB2, Informix, MySQL, MS SQL Server, Netezza, Oracle, PostgreSQL, Sybase, and others via ODBC/ANSI SQL

      Schedule ongoing metadata scans for the widest array of metadata targets, enabling automated data harvesting to update the catalog while leaving any enrichments in place. These capabilities, combined with lifecycle management, keep metadata current with full versioning and change management, reducing expensive manual tasks and rework.
  • entended support with more bridges
  • reverse engineer db
        mongodb, azure xml, add user defined properties
  • document model and extend with udps
  • complete compare
       Use the Complete Compare feature to compare the following items:


A data model with a different data model
A data model with a database
A data model with a script file
A database with a different database


  • forward engineer/alter
      Now that we’ve finalized our physical data model, we’ll want to create a physical database from it through forward engineering. Before we generate any code, however, we’ll want to validate our model to make sure that it will generate valid SQL structures for the database. CA ERwin Data Modeler has a process called Check Model which allows us to do a validation of the physical model before we reverse engineer. To run this validation, select Actions|Forward Engineer|Check Model from the Main Menu. A model validation report will be generated, as shown in Figure 19.79, which alerts you to any design errors in the model that will affect forward engineering[19].
  • source to target mapping
  • version control
       From release 9.0 onward, the way you access the Model Manager has changed. In fact the term Model Manager is also no longer used—it is now called the Mart. The Mart is built on a three-tier architecture, which includes a database, a web server, and a client. You may have seen the term MartServer in the installation documents and you may have looked for its meaning.

The term MartServer refers to the software that helps you connect a database to a client, through a web server. To understand this better, consider the Mart architecture as three layers of sheets, Sheet 1, Sheet 2, and Sheet 3. Assume that Sheet 1 is at the bottom and Sheet 3 is at the top.

Sheet 1 refers to the Mart database. You install database software and create a database to use as the Mart. It can be an Oracle, a Microsoft SQL Server, or a Sybase Adaptive Server database.
Sheet 2 refers to the web server. The web server is the software that connects the Mart database with the client. You can use the default web server (Tomcat) that comes with the Mart, or install a web server of your choice.
Sheet 3 refers to the client. CA ERwin Mart Administrator and CA ERwin Data Modeler both are clients. CA ERwin Mart Administrator is installed when you install Mart Server.
MartSever is not a computer, it is a software program. It helps you connect to the Mart database from CA ERwin Mart Administrator and CA ERwin Data Modeler, through Tomcat (default web server). When you install MartServer, CA ERwin Mart Administrator is installed.

hide unhide different versions.
  • reporting
   logical view: data flow to different entities, definition of entities. logical model, physical model.

No comments:

Post a Comment