UNDO/REDO  |   Big Database Support   |   Indexes with Included Columns   |   Reverse Engineer Improvement   |   PostScript Option   |  Bugs Fixed

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

In this release, our top features include:

– Added “Undo/Redo” feature in the tool

Long awaited feature of Undo/Redo is finally here. It is very simple to use:

  • Undo: Crtl + Z  OR  top tool bar icon
  • Redo: Crtl + Shift + Z  OR  top tool bar icon

– Big Databases Support

Supports big databases (with large number of tables) has been requested a lot, and we feel proud to announce we made this enhancement in this release.

Until now, SqlDBM was able to support up to 150 tables (before performance degrades), but now with this enhancement, SqlDBM can actually support more than 350 tables in a single diagram. Not only that, SqlDBM can actually reverse engineer big databases, which are up to 1000 tables (but on single diagram, user gets better performance up to 350 tables, so the preferred way is to split big databases into small manageable SubjectAreas/Diagrams).

 

– Indexes with Included Columns

There has been lot of user requests for support for “Index with included columns”. Hence we bumped up its priority and made it available in this release.

  • Users can create/edit Indexes with included columns options
  • Reverse Engineer existing diagram and get “Indexes with included columns” in SqlDBM

It is very straight forward to use, when user creates any index, then there is an option to add included columns as shown below:

– Enhanced Reverse Engineering 

We have made Reverse Engineering little smarter, now with this release after Reverse Engineer, tool does following:

  • Creates multiple diagrams, one full RE and then one for each Schma
  • If there are more than 100 tables in a diagram after RE, tool provides default view mode in “Table View” for better performance and more manageable diagramming

 

Post Script Option 

To cover all the unsupported database attributes, we have provided a window for our users so that can inject any SQL for each table, which SqlDBM would copy to SQL script during forward engineering. This would resolve the cases where users wants to store:

  • few insert SQL statements as a postscript of a look-up table, so that, whenever SQL is generated after Forward engineer these statements are always there
  • Trigger/Views/Functions definition SQL statements

 

– Bug fixed in Table Relationships 

We noticed that there was a bug (Rare Bug) in Table Relationships. Whenever there were Composite Primary Key (multi column PK) in a table, which was a Foreign Key to another table, and RoleName for these columns was used as existing column name of child table, then tool hides one of the columns in child table. Now this bug has been fixed. Please contact us in case you have any questions related to this, we would be more than happy to answer your questions. We believe the whole development team behind SqlDBM and all of its users as one big family, so want to keep things transparent.

 

– 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.

Related 

Load More