Re: What Database Best Supports Quick Retrieval Of One Child Table

Will Estes wrote:
>
> I have an application that has a parent record and up to ten million
> child records. I am guaranteed that for this application there will
> never be relational joins against other tables. In theory, which kind
> of database would best support these requirements, and which
> commercial product best instantiates the theory. The requirements
> are:
>
> - Must be able to very quickly create a new database and copy the one
> parent record and its ten million child records into the new database
>
> - Must be save against multiple-thread access (dozens of threads might
> be active against the same database at any one time)
>
> - Must be very fast for random access for read/write operations
> against individual child records
>
> - Locks on the child records must not lock the parent record or any
> other child (i.e., record-level locks, not page locks)
>
> Is a relational database the best kind for this sort of access?
> Which commercial database product will support these requirements?
>
> --
> Will Estes U.S. Computer
> Internet: westes_at_usc.com POB 3150
> Saratoga, CA 95070
> FAX: 408-446-1013
You live and work in Silicon Valley and you have to post this question in a newsgroup? You'll get as many good responses by rolling down your window at the next stop light and asking somebody. Or maybe lean over to the person next to you in MacDonald's the next time you're there.

John Received on Tue Jan 21 1997 - 00:00:00 CST