Modelers typically work from a common set of libraries, models, and submodels, and must be able to share information about these objects with other users. One way to share information is by using reports, which details the information and definitions for a model.
You can generate predefined reports to view the contents of specific libraries and models, view the changes and conflicts for specific models, and view the security structure for the database. You can use either the standard or customized reports to see detailed information for a specific model.
All users can run a number of reports in CA ERwin Data Modeler Workgroup Edition to view the contents of specific libraries and models, and use standard and customized reports to see model information in more detail.
Note: Some reports described can only be generated by the Mart Administrator.
CA ERwin Data Modeler Workgroup Edition includes the following predefined reports:
The following table describes the global reports that can be run against the mart:
Report Name |
Description |
---|---|
Attributes By Name |
Returns attribute information for a specified attribute name, including library, and its owning diagrams and entities |
Column Usage and Info by Name |
Returns column usage information for a specified column name |
Column Usage by Name and Definition |
Returns column usage information for a specified column name, including definition text |
Derived Models |
All models created using the Derive Model process |
Diagrams with Subject Areas |
All diagrams that contain subject areas |
Diagrams |
All diagrams |
Entities by Name |
Returns entity information for a specified entity name, including its library, its owning diagrams, and its owned attributes/columns |
Libraries |
All libraries in the mart |
Library Diagram Entity |
All diagrams, including all entities in use by a diagram, sorted by library |
Library Diagram Version |
All diagrams, including their versions, sorted by library |
Library Diagram |
All diagrams in a library, sorted by library |
Mart Domains |
All domains used by diagrams, sorted by diagram and library. Includes the domain name, domain parent, domain parent name, and domain data type. |
Subject Areas |
All subject areas, including subject area members, sorted by diagram for the current library |
Text Properties |
Text properties for all objects in use, sorted alphabetically by object class name, including each object name and property name, value, and sequence |
User-defined Properties |
All user-defined properties for the current open model, including UDP name, class name, and default value |
Users |
All users assigned to the mart, including user numeric ID and server login |
The following table describes the diagram reports that can be run against models the mart:
Report Name |
Description |
---|---|
Definitions |
All definition text for objects in the diagram |
Diagram Subject Areas |
All diagram subject areas |
Domains |
All diagram domains |
Entities |
All diagram entities |
Entity Attributes |
All diagram attributes that are included in an entity |
Entity PK FK |
All diagram primary keys and foreign keys by entity |
Entity Subtypes |
All diagram subtypes by entity |
Entity Supertypes |
All diagram supertypes by entity |
Entity Table Attribute Column Datatype Nulls |
All data type null values for entity attributes and table columns |
Index Members |
All diagram index members |
Index Properties |
All diagram index properties |
Relationships |
All diagram relationships |
The following table describes the model validation reports that can be run against models in the mart:
Report Name |
Description |
---|---|
Attributes without Definition |
All attributes that have no definition text |
Attributes without Domains |
All attributes that have no domain association |
Diagram Attributes without Definitions |
All diagram attributes that have no definition text |
Entities whose Primary Keys are all Foreign Keys |
All entities that use foreign keys as their primary keys |
Entities without Definitions |
All entities that have no definition text |
Entities without Primary Keys |
All entities that have no primary keys |
Many-to-Many Relationships |
All many-to-many relationships |
Unattached Entities |
All entities that are not part of a relationship, including entity name, diagram name where it is used, and library, sorted alphabetically by diagram name |
The following table describes other reports that can be run against the mart:
Report Name |
Description |
---|---|
Diagram Contents by Class |
Lists the contents of each diagram, sorted by object class |
Diagram Locks |
Lists the lock state of all open models in the library, including model name, lock state, user name, and user profile |
Note: Any changes you make to a diagram in the mart must be saved to the mart so it can be included in any reports you generate.
Report results are viewed and managed in the CA ERwin Reports Viewer. In addition to using the predefined reports available on the Tools menu, you can also use either the Bulk Editor to view and edit object properties in the current model and export results to a CSV file, or use the Query Tool to execute predefined or customized SQL SELECT statements against a model.
The Bulk Editor provides the selection, validation, and maintenance of model object metadata, permits reusable customization (option sets), and realtime access to model changes. Export results or selected rows to a CSV file. You can use the Bulk Editor to edit a small set of properties over a large number of objects. Changes and updates are immediately committed as you make them, field by field.
The Query Tool is used to query the repository through executing SQL SELECT statements against a local model or a model in the mart. You can use the Query Tool to create your own .QRY report file. Save your option set locally to the model or as an XML file. Export your results to a CSV file. You can execute a query against the objects and properties in the model, the metadata defining those objects and properties, and the action log that records the changes that are made to your model during the modeling session. You can create new queries or paste text from another source (such as a .SQL file) into a query. Although the Query Tool provides a built-in query interface in CA ERwin Data Modeler, you can also use any third-party reporting tool that has ODBC capability to query CA ERwin Data Modeler modeling data.
Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |