diagramming a database

[Olly]

Currently done via Viso.
I'd like to hide fields that aren't relevant or being used but be able to keep the diagram up to date by refreshing against the server.

Essentially an overlay of rules that hide fields and force relationships.

Please does anyone know of something out there, more free the better, that could do the trick.

Ta

[DimPrawn]

Would help if you said what database system you are using.

[Olly]

Would help if you said what database system you are using.

Okey doke - SQL server 2005
Though from a bit of a dig a few years ago it seemed most offerings were applicable to all major systems.
Still never found something simple and free enough. Actually found nothing that could do this kind of "overlay" hence the post.

[DimPrawn]

No idea.

[Olly]

so no knowledgeable folk able to spare a bit or er....knowledge?

purleaseeee

[HairyArsedBloke]

Doesn't Database diagrams in Management Studio with the Table View set to 'Names only' suit what you want?

[Spacecadet]

Doesn't Database diagrams in Management Studio with the Table View set to 'Names only' suit what you want?

I think he wants to do it in visio...

If there is no way to do this in visio then what you could do (as a bit of a hack workaround) is:
Rebuild the tables just for modelling purposes without the columns you want want hiding, then point visio at that.
Of course this then means you have 2 lots of tables to maintain, however it shouldn't be too big a job to write a stored procedure to do this for you

[AtW]

sp_help is all you should need.

HTH

[Olly]

Hmm...writing functionality that creates a copy and deletes the fields I'm not interested in would work. Extending that to put in "fake" relationship would be another matter and it wouldn't be ideal.

Funnily enough - this is the third organistation I've worked for that have this need....for a way to dynamically simplify and "correct" a database diagram.

viso is not a required tool, it's just that's how it's done now

[Spacecadet]

Hmm...writing functionality that creates a copy and deletes the fields I'm not interested in would work. Extending that to put in "fake" relationship would be another matter and it wouldn't be ideal.

Funnily enough - this is the third organistation I've worked for that have this need....for a way to dynamically simplify and "correct" a database diagram.

viso is not a required tool, it's just that's how it's done now

PM on the way