Cohen, Michael said:
> Thanks guys! I was figuring close to a million records potentially.
> I gather from Jochem's question that a million is not "prohibitively
> large?" :) Even to be querying on all the time?
It depends on the query patterns, but on properly sized hardware it
shouldn't be. Pre
ssage-
From: Cohen, Michael [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 7:30 PM
To: CF-Talk
Subject: RE: Data Model Design question
Thanks guys! I was figuring close to a million records
potentially. I gather
from Jochem's question that a million is not "proh
Any db fundamentals book
recommendations? Thanks again.
-Original Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Mon 11/10/2003 6:57 PM
To: CF-Talk
Cc:
Subject: Re: Data Model Design question
Cohen, Michael wrote:
> Say you've got a COURSE table that rep
> You would not want to have a single QUIZ table with a
> composite key of COURSE_ID and QUIZ_ID because potentially
> this table would become prohibitively large, correct?
While it might become large - very large, even - I don't think it would
become prohibitively large. The same is true for yo
Cohen, Michael wrote:
> Say you've got a COURSE table that represents many courses. New courses will
> always be being added to the table. Each course will have many quizzes and
> questions that need to be stored. You would not want to have a single QUIZ
> table with a composite key of COURSE_ID a
Say you've got a COURSE table that represents many courses. New courses will
always be being added to the table. Each course will have many quizzes and
questions that need to be stored. You would not want to have a single QUIZ
table with a composite key of COURSE_ID and QUIZ_ID because potentially
6 matches
Mail list logo
