DB Designer
#1 Database Design & Modeling Tool Online
- Website
- dbdesigner.net · all feeds from this site
- Feed URL
https://www.dbdesigner.net/feed/
Read it in your FeedListing reader
Or add to: Feedly Inoreader Raw feed
Latest posts
-
Soft Delete Database Design: Unique Keys and Safe Restores
Build a recoverable project schema without losing identity. Learn how PostgreSQL partial unique indexes, explicit restore rules, and parent-child lifecycle policies keep soft deletion predictable. The post Soft Delete Database Design: Unique Keys and Safe Restores appeared first…
-
Webhook Database Design: Events, Deliveries, and Retries
Design a webhook database schema that separates events, deliveries, and attempts. Explore PostgreSQL constraints, safe retries, transactional outboxes, and idempotency. The post Webhook Database Design: Events, Deliveries, and Retries appeared first on DB Designer .
-
Recurring Appointment Database Design: A Practical Guide
How to Design a Database for Recurring Appointments and Schedule Exceptions A customer books a workshop every Wednesday at 9:00 AM. Three weeks later, the instructor moves one session to Thursday. The following week is canceled because the building is closed. Meanwhile, several…
-
Designing Database Imports Without Losing Data Identity
How to Design a Database for External Data Imports Without Losing Identity A company imports customer records from three systems. The CRM contains mina@northwind.io. The billing platform contains mina.r@northwind.io. An older marketplace export contains the same person’s phone…
-
Snapshot Data Modeling for Historical Database Records
Why Historical Records Need Snapshots, Not Live References A customer places an order on Monday. On Friday, they update their delivery address. Nothing unusual has happened. Yet when support opens Monday’s order, the system now shows Friday’s address. The database is technically…
-
How to Model Approval Workflows in a Database
How to Model Approval Workflows in a Database Without Boolean Chaos A supplier application has been approved. Then its bank details change. Is the supplier still approved? The answer sounds like a business-policy question, but it quickly becomes a database design problem. If the…
-
Effective Dated Reference Data: Preserve Database History
When Reference Data Changes: Designing Database Codes That Preserve History A shipping database contains an order from 2022 with the delivery method EXP. Today, EXP means “Express Delivery — next business day.” But in 2022, the same code meant “Express Delivery — delivery within…
-
Designing Databases When Data Sources Disagree
When Your Data Sources Disagree: Designing a Database That Preserves the Truth A company is preparing to replace three old systems with one new database. The CRM says customer 1842 is called Northstar Labs. The billing system says Northstar Laboratories Ltd. A spreadsheet…
-
External IDs in Database Design: A Practical Guide
External IDs Are Not Your IDs: Modeling Identity Across Systems A backend team adds one column to the customer table: stripe_customer_id Six months later, another integration arrives: hubspot_contact_id Then the company migrates its support platform, imports customers from an…
-
How to Model Historical Relationships in a Database
When “Current” Lies: How to Model Relationships That Change Over Time A support manager opens a customer record and sees that the account belongs to the Enterprise plan. Nothing looks wrong. Then finance asks a different question: “Which plan was this customer on when the March…