Slashdot Mirror

← Back to Stories (view on slashdot.org)

Recommended Data Modeling Tools?

Posted by Cliff on from the charting-your-data-structures dept.

dnxthx asks: "After performing a fairly comprehensive web search (including Slashdot) I came to the (possibly incorrect) conclusion that there were no high-visibility sites that comprehensively reviewed and compared data modeling tools such as ER/Studio, ERWin, DeZign for Databases, System Architect, or Visio for Enterprise Architects. Since some of these tools can be quite expensive (ERWin is about $4K US it seems), I was wondering what the Slashdot community's experiences were with data modeling tools such as these, or some that our group has overlooked."

5 of 58 comments (clear)

  1. Data Architect by The Kompany by hotgazpacho · · Score: 4, Informative

    http://www.thekompany.com/products/dataarchitect/

    $60 USD for the download version. I used it for my last Database design project (first on MySQL, then moving that model to Postgres), and it was great. Made my life a lot easier. Available on Linux, Windows, and OS X.

  2. dia & tedia2sql by szap · · Score: 5, Informative
    We have been using dia and tedia2sql for many of our projects. This includes a project involving about a hundred tables, with foriegn keys all over, and a number of user defined functions (aka Stored Procedures) and aggregate functions.

    How it's done is, roughly, for a few related tables:

    1. Create tables using dia's UML's classes.
    2. Join the tables using UML Association to establish foreign keys.
    3. Set dia to autofit diagram into a number of pages.
    4. Add comments, draw pictures, whatever dia can draw.
    5. Save as an uncompressed XML file, chuck it into CVS. CVS likes text, so don't compress it.
    6. Optional: Print out pretty diagrams to printer. Dia's autofit is nice.
    Repeat above if you can't fit your tables into a set of nice looking pages.
    1. Create a Makefile to convert .dia to .sql using tedia2sql, and .dia to .eps using dia. (Left as an excerise to the reader). Bonus: autogen .eps to .pdf.
    2. Set up tedia2sql config to generate to your favourite rdbms. Or change Makefile to generate SQLs for each of Oracle, PostgreSQL, MySQL.
    3. Type 'make'.
    1. 5. Profit!

    Congrats! You have have fully printable, documentated, usable SQLs, and have version control on the schemas too. (Missing step is "4. Debug")

    P.S. tedia2sql is written in easily hackable perl.

  3. Re:random rants by 1001011010110101 · · Score: 4, Insightful

    One key point here is that most dbs that I've dealt with (Informix, MySQL, SQL Server & Oracle) do not let you specify the default value for a new column automatically. That means you're gonna have to script the modifications to insert/compute the new column anyway.

    Dont really know about the rest, but in Oracle you just do a

    create table foo (bar varchar2(10) default 'whatever')

    Not quite sure, but this sounds like ANSI92 to me.

    Of course, maintaint anything else than a 5 tables model by hand is a big PITA.

    And also, as a mini-rant, I have to say that the use of foreign keys has *never* been necessary in any db I've designed (and I have created very complex db apps with 30-70 well-connected tables).

    Well, that's just plain wrong. Declarative referential integrity saves a LOAD of work, makes your data model self-documenting, easier to maintain, and believe me, most modern databases know have query optimizers that work wonders on them.

    Of course, unless you charge by the hour, want to have to code on each of your 50 tables for such a basic thing as referential integrity, and want to make your database a pain to work with. If that's your objetive, you can also code primary key logic too :D

    My point here is that your accessor logic (so-called middleware) is what manifests the "foreign" relationship and if that's screwed then your app just doesn't work. Slowing the db down to do all that referential integrity is a waste of time. You've either got the middleware right or not.

    It really doesn't slow things much, as long as you have the proper indexes, which you should have in any case, as usually foreign keys in a data model represent relationships you are going to use to join different tables...
    This is, unless you are working with a very toy-like data model with 100 records on each table.

  4. Re:random rants by judd · · Score: 4, Insightful

    Just in case this isn't a deliberate troll to provoke database weenies:

    If you don't have referential integrity enforced via foreign keys, how do you know your "accessor logic" is correct? Or more importantly, how do you know when it's wrong? Trust me, if you do not enforce referential integrity you can have subtle problems that do not manifest until after you have corrupted your data, long before you're at the "just doesn't work" stage. (Eg, child records with no parents). It is far, far more sensible to leave this to the DBMS to manage and optimise the rare cases where this might cause performance problems. I'm sure you're a god who gets this right in every single case without the DBMS' help, but we mortals are better off leaving it to Oracle (or Postgres, or whatever.)

    And yeah, if you don't know what nulls are for, don't use them. /sarcasm.

  5. Builder.com Readers' Choice by superyooser · · Score: 4, Informative
    See the 2nd Annual Builder Readers' Choice Awards.

    The results for Best Modeling Tool (scroll to last chart) are:

    Eight other products are on the chart.