Re: how to implement a planing application

From: patrick guglich <guglichp_at_home.com>
Date: Sat, 07 Oct 2000 00:28:59 GMT
Message-ID: <f7uD5.91920$dZ2.37407031@news3.rdc1.on.home.com>

Have you considered denormalizing your database? If you just need to "keep appointments", a denormalized table would speed querys (ie: SELECTs) but make INSERTs slower. You could always make the denormalized table redundant to minimize this performance hit.
HTH
Patrick

"Arnold Douma" <douma33_at_zonnet.nl> wrote in message news:ayNz5.5270$tL4.113732_at_zonnet-reader-1...
> Can someone give me a database model for the next problem:
>
> There are persons (app 25) with individual working schedules. Within these
> schedules there have to be planed appointments. These appointments are
> segments of 10 min. long.
>
> How can i make a structure to implement this?? Just making a table with
> available time is an idea, but the database is getting realy big by that.
I
> have to keep appointments of the past AND the future year. This is going
to
> be a table with app 25 (persons) * 48 (timedivisions per day) * 365 (days
> per year) *2 (previous and next) = 876000 records!!!! So by a table of
this
> size, the response time is going to be a realy coffebreak.....
>
> Every solution or idea is welcome!!!!
>
>
Received on Fri Oct 06 2000 - 19:28:59 CDT