Saturday, January 7, 2012

SQL Power Architect

This is part of continuing set of reviews / opinion pieces about the state of data modeling tools that began over here.


I must say that SQL Power Architect came out of no where for me. I was googling around when I stumbled upon it and it sounded too good to be true. A multi-platform, open source database modeling tool with an Enterprise version available (for pay naturally) if you need advanced features. Watching some of the videos it sounds like this was a tool developed in house that evolved into a product for the company. I couldn't find much more history than that, if anyone has some let me know and I'll add it in here.

I was back to using my small (< 50 table) model and had no stability issues. Rock Solid.

SQL Power Architect: ~$00.00
SQL Power Architect Enterprise: $495.00

Common Checklist

  • Logic Modeling: Yes 
  • Physical Modeling: No 
  • Reverse Engineering: Yes 
  • Forward Engineering: Yes
  • Sub Models: No 
This is an interesting contrast to MySQL Workbench. SQL Power Architect insists that you do all of your work in the Logical Model (called the PlayPen Database) and generate SQL to apply to your Physical Model. Of course this gets awkward if you need to update your Logical Model from the actual database.

Once again Auto-Arrange is a very poor choice. So many of the relationships overlap that it is difficult to understand the model. 

There is no documentation for the Community edition available. To understand how this application works your best bet is to visit the YouTube SQL Power Channel and play around for a while. In all fairness the Enterprise Edition does have documentation available.

The GUI, well it is in Java, so it does not feel native. The scrolling is wrong, either it scrolls too fast or begins scrolling before you would expect it to. In most apps this is isn't a problem but as you're trying to work on your diagram this can get really awkward.

This is easily the best open source tool I've seen for data modeling. It is easy to setup, works with JDBC connections and allows you to compare and forward engineer your changes.

The downside is that all DB schema changes are expected to originate from it, or be added to the Logical Model manually. And the Logical Model does not support sub-models. And the GUI makes working with the models challenging.

These issues can be worked around by making a lot of small projects as sub-models. This raises it's own challenges with overlapping entities and synchronizing projects. 

All in all if you are working on an open source project with limited funds this may be your best approach but watch out, you will spend more effort managing this model than you expect.


  1. This is interesting! Hope you finish the reviews of the remaining 3 products. Thanks.

    1. I haven't been updating as much as I'd like, but I've been testing ER/Studio and ModelRight pretty extensively. I should have something up in the next few days.

      I'm glad you found these posts interesting, it's nice to know someone is reading it! :-)

  2. Plugging the power brick in bumps consumption up less than a watt for a total of about 5.7 Watts. This blog

  3. Free Valentina Studio works from a physical database and allows reverse engineer. If you are designing a logical model and plan to move to physical database, I found no way to do this with the free version.

  4. In general, there are two tariff levels, one for existing buildings and the other for new jobs. Download Drawings