SqlDBM Release Update – Oct 31, 2018

Advanced Reverse Engineering |   MySQL Reverse Engineering |   Bugs Fixed

The SqlDBM team is proud to announce the release of SqlDBM v.1.9 based on our roadmap/feedback.

In this release, our top features include:

– Reverse Engineering using SQL 

Long awaited feature of Reverse Engineering using SQL (instead of XML) is finally here.

Now users do not need to run any custom script to obtain database schema from MS SQL Server. Users can just inject DDL script (either existing or generated) to SqlDBM and have database schema in SqlDBM project. We have created a few help articles to describe on how to generate DDL script and use new style of  Reverse Engineering. Please check out small quick introductory video showing how to user new Reverse Engineering in SqlDBM.


– Reverse Engineering for MySQL 

In this version, SqlDBM released Reverse Engineering feature for MySQL projects. Now MySQL users, can bring their existing database projects in SqlDBM to improve, re-design  or visualize database projects. Reverse Engineering feature for MySQL project is very similar to MS SQL Server projects, it simply requires to inject DDL Script of your existing MySQL project.

Here are quick help articles explaining on how to generate SQL from MySQL Workbench and  use Reverse Engineering in SqlDBM


– Reverse Engineering on top of existing SqlDBM project

To resolve the issue, when developers directly alter database objects in the RDBMS, initial project in SqlDBM quickly becomes irrelevant because it gets out of sync from RDBMS and less usable for future designing. Therefore, the SqlDBM product team came up with a new and very useful feature, “Reverse Engineering on Top”, which enables developers to merge changes between initial SqlDBM model and RDBMS.

To use this feature:

  • just open existing SqlDBM project
  • go to Reverse Engineering tab
  • follow the steps to bring latest RDBMS version on top of existing SqlDBM project.


– Reverse Engineering: Table Options  & Import Options

While doing RE, there are options to pick and choose the table/s user wants to:

  1. Add to Project (if there are new tables in the DDL Script)
  2. Update (if tables are already existing with same name in the project)
  3. Delete (if tables are not in the new script, but exist in the existing project)


SqlDBM provides “Import options” in the right vertical bar, which lets user to pick diagram(s) where user wants new changes to appear in.


– Fixed following tickets reported on Support Forum


This isn’t all we’ve done, we’ve also made a few minor tweaks to improve the overall experience with SqlDBM.

Please check out SqlDBM at https://sqldbm.com, let us know how we can improve SqlDBM to resolve your current issues related to database designing/modeling. Help us get the next update to SqlDBM in the best possible shape. Your feedback is important to securing a solid update release, and we greatly appreciate your assistance.