We're excited to announce Diagram Views, a new feature that lets you create multiple customized views of your database diagram.

Now, you can filter out specific tables to highlight only the parts relevant to your current focus—whether it's a particular domain, process, or team discussion—all from the same underlying database structure that defined in your DBML code.

Why you’ll like it:

• No more overwhelming diagrams with hundreds of tables.
• Easily switch between views to share targeted insights, like a "Customer" for only customer-related tables, or an "Orders" view for sales workflows.
• Define one database structure and reuse it across multiple views.

Try it now:

• Open a diagram.
• Toggle table search panel (you can also press Cmd / Ctrl + F).
• Add a new view, and select your tables.

Note: Saving multiple views is a Personal Pro feature. On the Free plan, you can only filter tables and save these settings in the default view.

📚 Learn more →

Please give this feature a try and let us know what you think.

We’re excited to announce support for Microsoft Entra Single Sign-On (SSO)!

You can now log in to dbdiagram seamlessly and securely using your existing Microsoft credentials. This integration streamlines access for organizations and enhances security by leveraging Microsoft’s trusted authentication.

To get started, simply choose the Sign in with Microsoft option.

We’re excited to announce a powerful new feature in DBML — TablePartial!

Now you can define reusable sets of fields, settings, and indexes and inject them into multiple tables with a simple ~partial_name syntax.

Why you’ll like it:

• ✅ Write cleaner, DRY-er (Don’t Repeat Yourself) schema definitions.
• ♻️ Reuse common fields like timestamps and user metadata.
• ⚙️ Maintain consistency across your entire database with ease.

Start using TablePartial today to simplify your DBML projects and speed up your workflow!

📚 Read the full docs →

We hope these enhancements improve your database design and communication experience. Try them out and let us know what you think.

Valentine’s Day taught us relationships can be rock-solid or a little… optional 💔—and your database is no different! Our latest update lets you define optional or mandatory relationships, customize their colors, and add names to make your diagrams clearer and more meaningful.

Optional or Mandatory Relationships (free plan)​

Using the nullable constraint on the foreign key, we can now automatically determine whether a relationship is optional (zero-to-one/many) or mandatory (one-to-one/many) for the parent entity. Take a look at our example below:

Table follows {
  following_user_id int [ref: > users.id] // optional, many-to-zero relationship
  followed_user_id int [ref: > users.id, null] // optional, many-to-zero relationship
}

Table posts {
  id int [pk]
  user_id int [ref: > users.id, not null] // mandatory, many-to-one relationship
}

Custom Color for Relationship Lines (paid plan only)​

Make your diagrams more readable by assigning custom colors to relationships. You can either pick up a color directly in the diagram or define it via DBML with this syntax:

Ref: posts.user_id > users.id [color: #aabbcc]

If not defined, the relationship line will inherit the parent table’s header color by default.

We’ve also added a flowing animation to show the direction of each relationship.

Named Relationships (free plan)​

Label your relationships in DBML and see the names pop up on hover in your diagram! These hover-triggered names make it a breeze to identify connections without cluttering the view.

The syntax for naming a relationship is as follows:

Ref user_posts: posts.user_id > users.id

We hope these enhancements improve your database design and communication experience. Try them out and let us know what you think.

You can now set customized colors and add notes to table groups.

Table Group Color​

No more boring, grayed-out table groups that are difficult to spot when zoomed out, as you can now make them more colorful and distinct.

You can directly pick a color for your table group in the UI or use the following coding syntax:

TableGroup "Order Management" [color: #E74C3C] {
  ...
}

Table Group Notes​

Add Markdown descriptions for table groups to provide extra information, such as their purposes, specific details about child tables, and so on.

To add notes, use the following syntax:

TableGroup "User Wishlist System" [note: 'Manages the user wishlist functionality'] {
  ...
	
  // or use multi-line string to define Markdown content
  Note: '''
  This group manages the user wishlist functionality.
  - wishlists: Stores user-specific wishlists.
  - wishlist_items: Contains items added to each wishlist.
  '''
}

Both features are available as part of our paid Table Group feature set.

We believe this enhancement will greatly improve your database designing experience, and we look forward to your feedback.