📥Clone into existing diagrams

Previously you could clone any of your diagrams to start a new diagram. With this update, you now have a new option to append the cloned diagram into any of your existing diagrams, even into a diagram of another team (as long as you have the right permissions there).

Works for any template diagrams in our template gallery (that's coming soon) as well! 


Embed your database diagrams anywhere on the web!

That means it's much easier to include your DrawSQL database schema as part of your documentation now (e.g. in Confluence, Notion or any others), and not have to worry about syncing changes to keep it up-to-date. Some users have also started using this in their blog and Medium posts!

For now it's still missing the frontend 😬, eventually you'll get a nice interface to copy the embed code to copy directly to your site.

The frontend is ready now, just click on the 'share' dropdown in the top nav to get started!

🧮Support composite indexes and keys

Announcing support for composite primary & unique keys, as well as composite indexes comprising of multiple columns.

We're really excited for this one! To be honest, this took much longer than we'd like. What you're seeing is actually our 3rd-rebuild of the feature since we really wanted to nail the UX, by providing this additional functionality without compromising the minimal uncluttered feel of both the editor and canvas.

Also, the specified composite key/index supports ordering of the columns within. In most cases order won't matter, but in those few instances where it does for your app, it's good to know that your covered.

Let us know what you think, if you see anyway this can be improved further.

🧭Public roadmap

🤔💭Got a feature request or feedback for DrawSQL? It's now even easier to surface those thoughts on the newly launched roadmap: https://drawsql.app/roadmap

The roadmap also offers more transparency on what's in progress and what's in the pipeline. You can also upvote if you like an idea proposed by others.

Always love hearing from users!

🕰️Diagram Versioning

It's sometimes useful to tag 'checkpoints' for your diagram as it evolves, so that you can preview the previous state of a diagram, and revert to it if required.

We've got that covered now - you can now version your database diagrams!

Just tag a new version at any time:

And now you have a list of versions

🔒 This advanced feature is restricted to the 'growth' and 'enterprise' plan (yup they have just been renamed 😉). Upgrade now if you're not on these plans to gain access.

🕹️Editor configs - Defaults for new table color and column datatype

New workflow shortcut - You can now define defaults that will be automatically applied when you create new tables and columns. We're launching 2 of them now:

  1. Default table color
  2. Default column datatype

These can be configured within the new diagram settings popup within the editor.

This will be the last update to wrap up an awesome year. We're very excited for 2020 and have heaps planned, with the core of it to continue work with our loyal users drive new features, with every step to towards making DrawSQL the best tool for creating, planning and documenting your database schema.

Thanks for following along the journey 🙏, could not be where we are today without you. Happy new year 2020! 🎊🎉🍻 🎆

🐘Support for Postgres and 🧬SQL Server

A follow up feature from the previous update:

Back then when we envisioned for diagrams in DrawSQL to be 'DBMS agnostic', so users can create generic diagrams, and import/export them in any DBMS that they like.

While that's nice to have, however, we've learnt over time that for most apps out there switching the DBMS happens quite rarely. Making the editor be DBMS-agnostic had some limitations too - the major one that was causing headaches was that there wasn't a direct 1-1 mapping of column datatypes between the different DBMS. We tried a few different designs on the datatype selector to cater for this, but were not satisfied and felt like they were still unsatisfactory in terms of usability.

We've completed all the required changes for this Each diagram now has a single specified DBMS-type, and all functions from the column data type, import to the export formats will be automatically customized to fit the DBMS for that diagram. Hopefully the whole experience would be more streamlined for you now, regardless of which DBMS you're using.

Let us know what you think about this change 👍👎!

📥 Import from SQL script

After a month long of testing🚧 and patching🔨with a few selected users during the beta access period, this is now ready for the world!

Easily kick start your db diagram documentation by importing your SQL script. The importer will parse any "CREATE TABLE" statements to create the associated tables, columns and relationships.

🙏Thanks to all users that tried out the beta and provided feedback to shape this feature.

🖼️ Export as image

No more print screens or snipping!

Many users have been asking for a way to use the nice designs in DrawSQL for their project documentation. Happy to announce that you can now do so! The image export feature will allow you to download a .png image of your pretty diagrams.

Show Previous EntriesShow Previous Entries