Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread design question (date / time)
Wed, May 9 2007 8:18 AMPermanent Link

"Harry de Boer"
LS

What would be the best way (haven't done any testing, just curious if
there's a way to design it the best way from a pure logic point of view) to
design a table looking at amount of table (disk)space (ca. 2 million rows)
and queryspeed (to get from a certain date the earliest begintime and the
latest endtime):

1)
beginDateTime  TIMESTAMP
endDateTime    TIMESTAMP

2)
date                 DATE
beginTime        TIME
endTime           TIME

Can one figure out such a way (and what are the rules) or does it come down
to just testing it.

Regards, Harry

Wed, May 9 2007 5:45 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Harry,

<< What would be the best way (haven't done any testing, just curious if
there's a way to design it the best way from a pure logic point of view) to
design a table looking at amount of table (disk)space (ca. 2 million rows)
and queryspeed (to get from a certain date the earliest begintime and the
latest endtime): >>

I would say option 2) if you want to be able to search solely on the date
also.  It will be much easier that way and you could probably get away with
just an index on the date column alone if you'll always be searching on at
least the date column.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, May 10 2007 6:01 AMPermanent Link

"Harry de Boer"
Tim,

We'll be searching the date column a lot, yes,  so we'll go for option 2.
Thanks.

Regards, Harry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:F94C3BF9-D378-46E3-9FC5-D594EF80F2B7@news.elevatesoft.com...
> Harry,
>
> << What would be the best way (haven't done any testing, just curious if
> there's a way to design it the best way from a pure logic point of view)
to
> design a table looking at amount of table (disk)space (ca. 2 million rows)
> and queryspeed (to get from a certain date the earliest begintime and the
> latest endtime): >>
>
> I would say option 2) if you want to be able to search solely on the date
> also.  It will be much easier that way and you could probably get away
with
> just an index on the date column alone if you'll always be searching on at
> least the date column.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Thu, May 10 2007 8:24 AMPermanent Link

Mauricio Campana Nonino
Harry de Boer

Just one thing: if date can be different between begin and end, so you will have to go with number 1. If not, number 2 is better.

Mauricio Campana Nonino
Nonino Software

Image