Re: Database schema qurstion.

In article <sGPz5.4697$l35.106081_at_iad-read.news.verio.net>,   "Raymond R Cassick" <ray.cassick_at_vtg.com> wrote:
> Actually, that is the reason I am asking... I am doing some long range
> research on a ERP style project.
>
> Steve Long <steven.long_at_erols.com> wrote in message
> news:8qn40d$736$1_at_bob.news.rcn.net...
> > There are standardized solutions. They are called by various
 names, such
 as
> > "packaged software" or "ERP". Of course, one has to pay for having
 someone
> > else doing the work.
> > --------
> >
> > "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,

Wouldn't it be best to have variable length fields, so that you don't have to worry about how long the name field is?

> > > 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.
> > >
> > >
> >
> >
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Oct 05 2000 - 17:58:26 CEST