NVT Data Modeler, documentation

ER diagram-building

Building ER diagrams is one of the key functions of any database modeling tool. We've been striving for making the process of building ER diagrams really convenient for developers. NVT Data Modeler allows for focusing of the task of data modeling, with minimal effort needed for optimizing the positioning of entities and links on the diagram.

Forward Engineering

Forward Engineering is the feature that allows for generating a script for creating database objects in the language of the chosen RDBMS. The script is generated for the selected subset of data model objects.

Reverse Engineering

The Reverse Engineering feature extracts the description of the data model from the chosen database. It's one of possible ways of importing the data model into NVT Data Modeler as part of the initial migration from another database modeling tool. Developer teams, as well as information systems' customer companies can use this feature. NVT Data Modeller offers a convenient tool for selecting specific data objects and adding them to the data model incrementally.

Complete compare

The Complete Compare feature is also a key part of any quality data modeling tool. Complete Compare provides the ability to compare a data model with the structure of a database. The database operation element within NVT Data Modeler allows for various types of compare operations.

UNDO/REDO

NVT Data Modeler allows for reverting each and every data model modification operation, including diagram changes. Many lower-shelf data modeling tools don't support undo / redo operations, which makes them less attractive for complex data model work.

Auto-arranging objects in diagrams

The auto-arranging feature allows users to optimize the positioning of tables and their relationships within the diagram. Combined with the unlimited ability to create folderss and nesting levels, auto-arranging provides a way to bring order into a data model containing hundreds and thousands of tables.

Team collaboration in data modeling, with metadata stored in a repository

The repository is implemented as a Windows directory containing an XML file describing data model objects. Directories and files can act as data model objects. A directory serves the model structure by enabling an unlimited number of nesting levels in the model. A file is a description of an ER diagram, a table, or a view stored in an XML-based format. File names match names of data model objects. The repository can be stored in your preferred version control system. Only modify those of the data model files that are related to the problem at hand. Work as a team on a data model that can contain thousands of data tables.

An expanded physical data model

The physical data model supports a property called "Logical Name" for each data table and attribute. Logical Name allows for adding a brief description of the entity or attribute, which can eliminate the need for defining conceptual and logical data models in the majority of use cases. When necessary, Logical Name values can be used for auto-documenting the DB.


Recording data model changes as DDL scripts

The most common use case in data modeling tool usage consists of making a change in the data model, followed by preparing scripts for applying the change to the database. NVT Data Modeler offers the unique capability for generating

A version control system is used for storing the history of modifications in the data model and developer team collaboration

Storing diagrams and data tables as separate files allows us to minimize conflicts among multiple users accessing the model. NVT Data Modeler has built-in support for version control systems that support SCC API (Microsoft Source Code Control API) interface. For developers utilizing Oracle RDBMS, NVT Data Modeler provides NVT Version Control - a built-in version control system which stores the server-side version of the repository within Oracle.

Fast object search

Search operates on both the data model and the opened databases.

Tight coupling with RDBMSes. Simultaneous work with multiple DB instances

NVT Data Modeler can simultaneously connect with multiple databases. This can be useful if a model contains a description of databases located on more than one server. Each database connection generates a separate tab that contains a list of all the specific database's tables. When working with a list of tables, the following functions are available: search; global or local comparison of table structures with the data model (Complete Compare); adding missing tables into the data model (Reverse Engineering).

Data model import from Erwin, SQL Developer Oracle Data Modeler

Erwin data model import allows users to load metadata and diagrams developed in other tools. The affordability of NVT Data Modeler, combined with the availability of premium features, typically out of reach for users of cheaper tools, suggest the need to migrate existing data models and switch to NVT Data Modeler.

Generate a table structure report in MS Word format

High-cost data modeling tools often allow for building complex reports that represent one or another aspect of the data model. We've used these tools and found that despite the complexity of the report generation machinery, the required formats of presenting information are not always within reach. We find that the one and only MS Word - based presentation format ised by NVT Data Modeler typically completely satisifies our customers' needs.

Export selected diagrams and tables as images and XSD schemas

The task of system integration has consistently grown in importance. In order to eliminate dependencies on specific data models, data is exchanged in the shape of XML streams, generated within the specific system. The commonly accepted way to define and communicate XML stream structures utilizes XSD schemas. NVT Data Modeler can export table structures in the XSD format.