Ever seen a table with so many columns you wonder if the designer had fallen out of the de-normalization tree and had hit every branch on the way down? Oracle currently allows a max of 1,000 columns per table. Please do not test this limit. Maybe you do need that many columns, but I doubt it.

If you were to visualize this data model, imagine how easily you might be overwhelmed with all the white-noise, or extra information.

In an earlier post I advocated using SubViews to alleviate the headaches you get when working with many hundreds or thousands of entities.

Well maybe you only have several dozen entities but the number of attributes is overwhelming.

So just hide them

A new feature in v3.1 – now in Early Adopter Release – allows you to auto-hide attributes that don’t meet the following requirements:

Just show me the 'important' stuff

Model TMI

Modeling TMI? There's a medicated cream for that.

The Goldilocks View

After you apply the model view options, the ‘extra’ attributes/columns will be hidden. However, the entity objects in the diagram will still be REALLY big. So just right-mouse-click and use the ‘Resize objects to visible’ call.

Ah, that feels so much better! And my eyes thank you SQL Developer!

What else is new in v3.1 and where can I go get it?


I'm a Distinguished Product Manager at Oracle. My mission is to help you and your company be more efficient with our database tools.


  1. Avinash Mehta Reply

    How to exclude a column from a ddl export in sql modeler?

  2. Avinash Mehta Reply

    How to exclude a column from a ddl export in sql developer?

  3. Wow, that’s what I was searching for, what a material! present here
    at this website, thanks admin of this site.

  4. Hello,
    I have a big problem with inheritance, identifying relationship and pk.

    I have
    tableA with pk : id_A
    tableB empty.
    tableC with pk : id_C

    I make a relation (identifying relationship) between tableA and tableB( tableB will receive the pk of tableA),
    until now everything is ok!!!

    tableB is a subtype of tableC ( tableC is a supertype of tableB), so normaly it will have also the pk of tableC.
    until now everything is ok!!!

    The problem is that:
    When I pass from the logical to the relationnal model, the first pk of TableB (I mean idA) turn to “unique Key” not a primary key) and I have only id_C as a pk .

    I want to to have a pk with the two ID , I mean (id_A,id_C).

    I know how to change it after the generation of the relational model but I want to do it automatically from the logical model.

    Please excuse my bad English.

    Thank you

  5. Once I resize all my entity objects are far apart, is there a way to bring them all together? or do I need to do it manually ?

Write A Comment