Started using dbDoc and dbDiagram few days ago.
My company bought Informatica MDM (not going to post the price here but lets say it cost me an arm and a leg and my firstborn) . With dbDoc and diagram i can do 80% of the work we are doing with MDM tool.
Next step is to upload our entire data model 10 data bases and around 3K tables. Any advice on best practices.
Jay
1 Like
Hi Jay,
Glad to hear you’re seeing that much value already! Scaling to 3,000 tables across 10 databases requires a bit of strategy to keep things snappy. Here are two best practices:
- One Database per Project: I highly recommend splitting each of your 10 databases into its own separate project/file. This significantly optimizes performance and prevents “schema bloat.”
- Use Diagram Views: Within each database, use Diagram Views to scope tables by domain (e.g., Finance, Users, Logistics). This gives you a much smoother UX by letting you focus on specific modules rather than 300+ tables at once.
Since you’re dealing with such a large scale, automation is your friend. Setting up a CI pipeline to push these updates will save you a ton of manual effort as those 3k tables evolve.
Best Regards
Huy Phung
I popped in here after deleting all my diagrams.
Call me stupid but I never noticed the default for the free tier is for all my diagrams to be publicly available and only after thinkering to realize that locking them costs money.
I respect the fact you need to earn a living but you should emphasize a bit more that the default is for the user work to be public.
thankfully I never used it for something crucial.
Hey @Avi_Koenig, thanks for the honest feedback — this is really fair.
You’re right that public-by-default on the free tier isn’t communicated clearly enough, and we don’t want anyone surprised about their diagrams’ visibility. Sorry for the confusion.
Good news: we’re actively rethinking this. We’re working on updating our pricing models, and how privacy fits into the free tier is part of that — so this may well change down the road. Can’t share specifics yet, but it’s on our radar.
Thanks again for flagging it.