Re: Database schema qurstion.

One would think that there are standard solutions to common problems. The issue is that common problems aren't common enough to have a standard solution, so it is actually easier to design from scratch each time than to try to adapt a "template" to meet the individual peculiarities of each business problem.

"Raymond R Cassick" <ray.cassick_at_vtg.com> wrote in message news:8iqx5.2263$l35.48076_at_iad-read.news.verio.net...
> I am doing some research for a new product and am at the point where I am
> starting to look at the DB design.
>
> I need to store information (obviously) ranging from customer data to
> accounting data.
>
> The big question that I have is.... Has anyone done ant research on the
> best schema to use for specific instances? I mean, if I want to store
> customer data, how long does the name field have to be, how should the
> fields be grouped together in tables to make best use of indexes, etc...
>
> There HAS to have been some kind of study done with this in mind
 somewhere.
> I just can't find it.
>
>
Received on Wed Sep 20 2000 - 00:00:00 CEST