In the early phase of data modeling how do you usually start with
these steps:

data layout, normalization, key definition, and performance tuning

Considering that application needs to design from dcratch and it is
100+ tables involve

<soalvajavab1 (AT) yahoo (DOT) com> wrote

Here is an outline to data modeling:

http://www.utexas.edu/its/windows/da.../overview.html

You probably want to get a book with more detail in it, but this is a
start.

On Apr 26, 3:59 am, "David Cressey" <cresse... (AT) verizon (DOT) net> wrote:
The web site was fgreat. Thanks a lot.

JUst want to know also What is your favourite book for this matter?
well written, practical with examples?

On 26 Apr 2007 09:15:09 -0700, soalvajavab1 (AT) yahoo (DOT) com wrote:

This response does rather explain why usenet is dying, doesn't it?

Lemming
--
Curiosity *may* have killed Schrodinger's cat.

soalvajavab1 (AT) yahoo (DOT) com wrote:
should support.

Then identify business objects and their relations.

This is just one possible solution. There are many methods. Defining
the business rules should always come first. You can not design
anything unless you have some requirements. Some people would say to
map out the processes. Depends how large and complex the scope of the
design is and how well you have to write up the specification.
Oversimplification can cause problems later. The trick is to identify
the hidden requirements, that the customers have overlooked.

One mistake in the design is you are designing a system to get
information out, not put data in.