Be part of SqlDBM’s team by Supporting Us on Pricing Page.
The SqlDBM team is proud to announce the release of SqlDBM v.22.214.171.124 based on our roadmap/feedback.
In this release, our top features include:
– Introducing way on How to: Say “Thank You” OR Bump feature priority OR Keep us going
We have received a lot of feedback, on how soon we will have all the key pending features like Print, Compare Revisions, Views/Triggers , Oracle/PostgreSQL support etc, basically to create best database design solution. Well, to accomplish this common goal quicker, we need all of your support to join hands with us. We highly encourage you to participate in our campaign of “Support Us”.
Check it out at https://sqldbm.com/en/Pricing/
– Social Share
Now users have ability to quickly share SqlDBM on Social platforms like Facebook, LinkedIn, Twitter and Google+.
– Updated Collaborate feature
Now, when user locks the project, SqlDBM tool will re-load the project with latest version. This is done to avoid user to inadvertently work on older revision.
– Context menu
- Added Context menu for Relationship lines and Notes
- Updated Context menu for Tables:
- To make it more clear, menu title for “Remove” is updated to “Hide”
- Shortcut Keys for context menu “Remove” and “Delete” are updated
– Other updates
- Show busy icon during ‘Project Loading’: Enhanced the user experience by showing busy icon.
- Updated account lockout message: Whenever account is locked out due to multiple failed authentication attempts, account is locked out for 5 minutes.
- Latest Revision Remark: In case user opens older revision, now there is a link for latest version next to Project Name in the tool. This is done to avoid user to inadvertently work on older revision and overwrite the latest revision.
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.