- Three types of data models: Conceptual, Logical, and PhysicalA well-designed model increases both efficiency and data quality, and can be easily understood by a wide variety of audiences. Navicat Data Modeler 2.1 enhances communication and collaboration between business and information-technology professionals by providing the ability to design conceptual, logical, and physical models. You can draw your own shapes, lines and labels using the comprehensive range of drawing tools to enrich your model design.

- Navicat CloudSync your models and virtual groups to the cloud so you can get real-time access to them anytime, anywhere. With Navicat Cloud Collaboration, you can create, organize and share files/projects with your coworkers from anywhere, on any device.

You can take control of your project -- adding members you choose, defining the role of each member, and get visibility into your team activities from the Activity Log to align your team for greater productivity.

2.0.4

2.0.3

- New user interface design- Support 3 model types - Physical, Logical and Conceptual.- Support MariaDB databases.- Support Views in Physical Model.- Support Model Conversion.- Support to sync model files and virtual group information to Navicat Cloud.- Support adding shapes.- Enhanced Table Designer

1.0.7

Mar 11, 2015

Minor bug fixes

1.0.6

Dec 2, 2014

Fixed the stability issue when running on Mac OS X 10.10

1.0.5

Aug 15, 2013

- Minor bug fixes

1.0.4

Jun 23, 2013

- Some minor bug fixes

1.0.3

Jan 15, 2013

- Fixed some minor bugs

- Supported purchasing features through In-App Purchase

1.0.2

Jul 2, 2012

May 4, 2018

Version 2.1.18

Bug fixes and improvements

Ratings and Reviews

Product is unusable for existing databases

Aug 17, 2015

AnoPres

While the app is visually appealing, it currently has a serious show-stopper if you want to use it to document an existing MSSQL database. It currently has no way to create a primary key on a table and set it as an identity field. That by itself could be worked around as long as you could make the setting in SSMS, but the app also can’t update an existing model. You have to create it from scratch each time you make a change in the actual db. This prevents you from doing anything other than auto-generating your model if you intend to use it in conjunction with the actual db.

Hopefully a fix is forthcoming.

Product is unusable for existing databases

Aug 17, 2015

AnoPres

While the app is visually appealing, it currently has a serious show-stopper if you want to use it to document an existing MSSQL database. It currently has no way to create a primary key on a table and set it as an identity field. That by itself could be worked around as long as you could make the setting in SSMS, but the app also can’t update an existing model. You have to create it from scratch each time you make a change in the actual db. This prevents you from doing anything other than auto-generating your model if you intend to use it in conjunction with the actual db.

Hopefully a fix is forthcoming.

Just Meh.

Jan 14, 2015

ubergeek1989

For the fact that this is the only DB modeler on the App Store (I could find), this is still terrible. For me, I find that all DB Modelers should work just like MySQL Workbench. I don’t always use MySQL, but I can use Workbench regardless. I can’t find a good reason to keep this on my Mac. The interface isn’t very intuitive. Context menus appear in random locations on screen. The tables and notes are clunky.

Just Meh.

Jan 14, 2015

ubergeek1989

For the fact that this is the only DB modeler on the App Store (I could find), this is still terrible. For me, I find that all DB Modelers should work just like MySQL Workbench. I don’t always use MySQL, but I can use Workbench regardless. I can’t find a good reason to keep this on my Mac. The interface isn’t very intuitive. Context menus appear in random locations on screen. The tables and notes are clunky.

Problems with Foreigh Key dialog

Oct 7, 2015

Davelsumner

This version has a problem with the foreign key diaolog. It stores links the wrong tables and fields, making the foreign keys unusable, when you have more than one foreign key in a table. Hope to get an update soon for this.

Problems with Foreigh Key dialog

Oct 7, 2015

Davelsumner

This version has a problem with the foreign key diaolog. It stores links the wrong tables and fields, making the foreign keys unusable, when you have more than one foreign key in a table. Hope to get an update soon for this.