Is drawing a final diagram of the whole database a crucial thing to do? I think writing a verbal plan/steps is sufficient..
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I've always found the diagrams a tad cumbersome for larger databases.
I find linked database documentation easier to read and see.
Apex SQL Doc does a very good job of this compiling a linked HTML help file of the database where you can follow contraints, keys and so on from parent to child very easily.
There may be others out there but I found this one very easy to use.
Their Edit tool rocks too. (sales pitch over ;)
I find this product's documentation better for beginners
http://www.leadum.com/sql-
Sample:
http://www.leadum.com/down
Just an opinion...
Yes, the DAB documentors create documentations based on an existing DB.
For pre-emptive design work you will probably be looking for a data modeling tool. Though a lot of them actually connecto to an existing database for thier models.
There's a list of various database tools for modeling, ERD etc here: http://www.databaseanswers
One that I didn't see on that list is: http://www.databaseanswers
Ok, good answer but i'm confused. I don't see the difference between date modeler, doc app, and er diagram tools. All of them end up creating a documentation in different formats on an existing DB, so why should developer bother and use data modeling tool while the developer knows he can save time by just plan on paper then implement physically. Until DB is done structured physically, export the documentation for future references. Isn't this a better solution than data modeling for pre-emptive design work?
I'm a bit bad and have pretty much done the design in my head or on the fly doodling on bits of paper for people when asked.
I have been on fairly simple projects though and have a pretty standardised, reusable schema design for the main elements.
There are modeling tools out there to use from the word go.
Enterprise Architect is one where you design both the DB structure and code objects within it.
From the DB side you then just pick your DB vendor and it generates the DDL for the tables based on your design.
I don't think it's cheap however and how far yuo go all depends on the size of the company, project and development team.
Business Accounts
Answer for Membership
by: DanielWilsonPosted on 2009-08-12 at 14:42:08ID: 25083354
Many developers find an ER diagram communicates the relationships between tables far more clearly than a verbal description of the DB.
Is it crucial? Well, not as crucial as a good design in the first place. But if you're going to produce documentation for the benefit of future development, an ER diagram would be one of the more important pieces, assuming the DB is of much complexity at all ... say more than about 5 tables.
Others may disagree, but those are my thoughts :)