TMS Data Modeler

TMS Data Modeler is the ultimate tool for modeling databases with an easy and simple interface.

It provides powerful features you need, such as diagramming, reverse engineering, SQL script generation and version control.

It keeps track of your changes and generates SQL scripts to update your database according to them.

It has smooth integration with development tools like Delphi and C++Builder.

And all of these features are accessible through a very pleasant user interface.

Supported databases

• Absolute Database
  
• ElevateDB
  
• Firebird 2
  
• Firebird 3
  
• MS SQL Server 2000
  
• MS SQL Server 2005
  
• MS SQL Server 2008
  
• MS SQL Server 2016
  
• MS SQL Azure
  
• MySQL 5.1
  
• MySQL 5.7
  
• NexusDB V3
  
• Oracle 10g
  
• PostgreSQL
  
• SQLite
  

Feature Overview

Entity relationship diagram editor (ER diagram)
Design ER diagrams using Data Modeler. You can add tables to the diagram, see the relationships, change several display options, and much more.







Create tables in diagram and/or in tab forms
If you don't want or don't need to model your database using diagrams, you don't have to. Data Modeler allows you to create and manage database objects directly, without having to deal with visual diagram designing. It's up to you.
Multi-diagram interface
Create different ER diagrams in a single project. You can put different tables in each diagram, making it easy to document and separate your application if it's too big.
Project validation allows you to trace errors in your model
Data Modeler performs a validation in your database model checking for design errors.

It also displays warnings about your project, such as usage of reserved words and tables with no primary keys, among others.

This validation allows fine tuning of your database model, and avoids future problems after your software is in production.







Supports logical (application-level) domains
Use domains as an abstraction layer for your data types. Even if your database system doesn't support domains/user-defined types, you can do it at application level in Data Modeler and make it easy to maintain your databases.







Manage many database objects
You can use Data Modeler to manage not only tables and fields, but several other database objects. Data Modeler supports indexes, triggers, relationships, constraints, views, procedures, generators, etc. Each database system has its own set of objects available.







Several database systems supported and more will be added
Data Modeler supports a number of database systems and new ones are in our roadmap to be included in future versions. Reverse engineering of existing databases
Import your existing databases and start using Data Modeler quickly. The reverse engineering tool connects directly to your existing database and extracts all the information you need, such as tables, fields, foreign keys and other objects.







Generate SQL (DDL) scripts to create databases
Use Data Modeler to generate the SQL script that will create all your database objects. You can choose which object types to generate.







Keep track of your changes by archiving and managing versions
With Data Modeler you can archive project versions/add checkpoints. This way you can have the history of all development stages of database modeling, and also compare between versions and see what has changed from one version to another.







Compare models between versions or between projects
A full comparer is available for you to check the differences between two models.

You can perform comparison between two versions, or even between two projects.

The comparer provides a very friendly visual interface that shows the differences in a tree view and also in a SQL diff format.

From the comparer you can choose which items you want to update to generate an Alter SQL script.







Generate Alter SQL scripts to update database according to changes
Data Modeler creates SQL scripts to alter your database and update the structure. By using the comparer and/or checking differences, you can easily generate the alter script related to the differences and have your database in sync with your project.







Convert model to a different database system
If you want to target multiple database systems, you can easily convert your project from one database system to another. Data Modeler provides data type conversion maps between the databases, and allows you to create your own custom conversion map.







Modern ribbon interface
Data modeler is one of the few database modeling tools that offers the modern ribbon interface. It's much easier to use, nicer to look, and all options and features are available with less menu clicks.



Tables and other objects organized in tabs
Don't edit your tables, fields and objects in modal forms or windows that overlap each other.

Most tables and objects in data modeler are displayed in tabs, making navigation very similar to browsers like Firefox and Internet Explorer.

You can have many objects open at the same time, all accessible through one click.



Easy and quick navigation. Create tables and fields in a glance
Everything in Data Modeler was designed to be easy. Objects are displayed in tabs, and creating and editing fields don't require you to open another window. Everything is simple, clean and accessible through keyboard in a single window. Create your tables and fields quickly.







Multi-project interface
Open several projects at the same time. And you don't need to deal with MDI interfaces. Every project has its own taskbar button and you can easily switch between projects using regular Windows Alt-Tab function.







https://www.tmssoftware.com/site/tmsdm.asp

v3.3.9

• Fixed : SQLite import was failing when -- comments were preceded by parenthesis
  

v3.3.8

• Fixed : SQLite trigger procedures were being generated in a single line
  
• Fixed : SQLite import was failing when field identifiers had non-Latin characters
  
• Fixed : SQLite import was failing when -- comments were preceded by comma
  
• Fixed : SQLite import sometimes was incorrectly importing the referenced field in a relationship
  

v3.3.7

• Fixed : Error "column reference 'oid' is ambiguous" when importing PostgreSQL 12 databases.
  

v3.3.6

• Improved : Support for XMLType data type in Oracle.
  

v3.3.5

• Fixed : Before generating DROP COLUMN statements in SQL Server, it's now generating DROP CONSTRAINT statements associated to the column.
  
• Fixed : "More colors..." option was not working for fill and text color of diagram objects.
  

v3.3.4

• Improved : Added support for range types in PostgreSQL (daterange, int4range, etc.)
  

v3.3.3

• Fixed : Firebird 3 did not include data type "Numeric (Identity)"
  

v3.3.2

• New : PostgreSQL 11 support, avoiding the error "p.proisagg does not exist. perhaps you meant to reference the column p.prolang"
  

v3.3.1

• Improved : Arguments for OnClassGenerated event now includes references to Table and Sequence attribute. Used in the example Adding Schema Name to Table Attribute.
  
• Fixed : Performing project checking in ElevateDB projects now reports wrong field size for char/binary fields with size higher than 1024.
  

v3.3

• New : "Scripting" button in Tools tab in ribbon, opens a full scripting IDE for low-level and advanced manipulation of the existing data dictionary.
  

v3.2.6

• Improved : List of tables in the Generate Script dialog is now sorted.
  
• Fixed : PostgreSQL database importer was not correctly retrieving foreign keys with same name in different tables.
  
• Fixed : Fields in primary keys were being nullable when using nullable domains. It broke backward compatibility, fields in primary keys should always be not null.
  

v3.2.5

• Improved : There is now a check box "Specific" for the "Not null" field. When the field has a domain associated to it, this new check box allows explicitly control if the NOT NULL flag should come from domain or you would want to ignore the domain setting and use a specific value for the field.
  

v3.2.4

• Fixed : Foreign keys with multiple fields (relationships with composite keys) not being correctly imported from Oracle databases.
  

v3.2.3

• Fixed : Project window maximizing automatically in some situations.
  
• Fixed : Null/NotNull checkbox was disabled for fields associated with logical domains.
  

v3.2.2

• Fixed : SQL Server ALTER TABLE ADD COLUMN statement was not including constraint name for default values.
  

v3.2.1

• Fixed : Firebird behavior with domains: size, not null and constraint was not being retrieved from domain.
  

v3.2

• New : Support for Interbase 2017
  
• Fixed : Firebird/Interbase connection was not working in some situations
  
• Fixed : Error when importing MySQL 8 databases (Table 'mysql.proc' doesn't exist)
  

v3.1.2

• Fixed : Data Modeler version information in VCL Subscription Manager showing incorrect after automatic update.
  

v3.1.1

• Fixed : SQLite database import was wrongly considering SQLite "TEXT" datatype as a (char) blob. Now it's considered as regular string (VARCHAR).
  
• Fixed : Importing SQLite tables with field names starting with number was raising error.
  

v3.1

• New : Database metadata objects available in customization script events.
  

v3.0.3

• Fixed : Connecting to MS SQL Server LocalDB was raising an error "SQL Server does not exist or access is denied"
  

v3.0.2

• Fixed : Exporting descriptions with single quotes to Aurelius classes was generating invalid Pascal code. The single quotes are now duplicated to form valid Pascal strings.
  

v3.0.1

• New : OnUnitGenerated event in TMS Aurelius Export customization script.
  
• Improved : Table list in Mappings Tab of TMS Aurelius Export Dialog is now sorted in alphabetical order.
  
• Improved : Added OID type for PostgreSQL databases.
  

v3.0

• New : Source code preview in Aurelius export.
  
• New : Option to export TMS Aurelius classes to several different units.
  
• New : Modern User Interface.
  
• New : Model names in TMS Aurelius export.
  
• New : Customization scripts in TMS Aurelius export.
  
• Improved : Documentation has received a significant review.
  
• Fixed : Checkboxes for defining specific default and check constraint were not being enabled correctly.
  
• Fixed : "Access Violation" error when clicking Exit or double click menu button.