Re: Depicting a database schema

I understand why you want it to be quick, but why do you want it to be dirty?

This may sound flip, but I'm serious. If you take an extra half day to get the objects in the schema
designed right, you may save a half a year worth of knotty programming and administration
problems. This of course, depends on how ambitious the application turns out to be.

There are design disciplines for database design, and failure to follow them, without a good reason, usually leads to more trouble than it's worth.

Do you know what server is going to run your database? Do you know what datatypes that server supports? Do you have a good conceptual model of the information storage and retrieval requirements? Can you use that conceptual model to pick a datatype for each column of your data?

Do you know design principles like data normalization and/or star schema? Do you know when to apply these principles? Do you know what happens when you go against these principles? Do you care? Should you care?

These are all legitimate questions, with more than one possible answer. I wish you well.

res038qs wrote in message ...
>Can anyone give me an example of how to lay out a database schema?
>I have a small set of data in approx 6 tables and I want to represent
>the tables, keys, datatypes, lengths and domain info......
>
>Does anyone have a quick and dirty approach for doing this?
>
>Thanks in advance
>k.paul_at_gte.net
>
>
Received on Sat Sep 02 2000 - 15:56:58 CEST