Data Modeling Tool Alternatives
My workplace has none of the traditional data modeling tools. And systems are locked down so that I cannot download even the free demo versions. It also seems unlikely that any tools will be available anytime soon. Any ideals on how to develop a presentable data model without the traditional tools?
Locked down workstations can be troublesome. While not begin able to run installers, some applications come as portable apps to circumvent this privilege issue.
Oracle SQL Modeler is free and feature-rich.
You can drop in JDBC driver and talk to MS SQL, PostgreSQL too for the physical model.
Nobody knows more than https://www.thatjeffsmith.com/data-modeling/
Looks like Oracle's free SDDM tool may have fixed your problem?
If you really cannot install anything on your company laptop, I was going to suggest Vertebelo as well.
But if you can convince them to let you install something...
At every client and employer I've worked at since '99, ER/Studio has won the evaluation and was selected.
At my current employer there was no budget for that big of a tool. The tool that took second place in our 12-tool eval, was a cheap modeling tool named DbSchema. Erwin took third. Although DbSchema is missing some rather large feature sets that ER/Studio and Erwin offer (like a repository), there are other things it sports that made life so much easier for me and our team, that we have learned to do without the enterprise-grade features. DbSchema connects to pretty much every database known to man, about 10 of them natively. We needed Oracle, Postgres, MongoDB and Snowflake, all of which it does out-of-the-box without paying for extra connectors like ER/Studio. The visual interface is sharp and works the way I think when it comes to submodels. They have been very responsive to issues we have submitted to support, and listen to our opinions. Probably my favorite is not fiddling with relationship lines anymore, when arranging the layout to look pretty. It's fast and looks great. Because it re-adjusts the lines automatically if you move an entity, it does seem to slow down when dealing with a huge schema of tables (400 to 1000 or more) which was freshly reverse-engineered. Once you break that mammoth up into the functionally-related submodels (which they call Layouts), then it seems to work fine again. One of my favorite things is how the model is kept in a single XML file. This has made mass changes and other tasks child's play when the model file is textual instead of binary. Last time I played with Oracle's SDDM, the model was spread out over something like 2,000 XML files for a big schema. That was a show-stopper for me. This single XML file has so many advantages, including the easy diff comparison during pull requests in GitHub. Anyway, we really like it, despite a few little bumps along the way. $63 academic, $127 personal, $197 commercial. Not affiliated in any way. Just fans.