<p> I&#39;m not usually much of a &#34;visual&#34; guy. I&#39;d rather read a text description of most stuff than look at pictures.</p> <p> The one great exception to this is when it comes to modelling large databases–say, more than 10 tables. At that point, staring at line after line of SQL simply doesn&#39;t cut it–I can&#39;t discern the problems at a glance, there&#39;s lots of paging around, etc.</p> <p> For the moment I use the UML mode of <a href="http://www.lysator.liu.se/~alla/dia/">Dia</a>, which is an OK tool, plus a custom XSL stylesheet for coverting the Dia&#39;s output into SQL. It works OK–you do get a diagram out of it, and you can coerce it to produce decent SQL–but it&#39;s just not…fluid. There&#39;s a lot of fiddly stuff that requires very careful work, and supporting things like foreign key references always requires more work than it should. This makes creating the diagram that much more work and frustration.</p>