Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Why bother with a database if ...
If I may ask, why store all of the data in a single queue? You could achieve parallel processing by simply having the collection process perform a round robin distribution to (n) files and an instance of the final process run against each file.
Of course, you can implement a similar
technique within the database and still
have transaction management.
-- Michael D. Long http://extremedna.homestead.com "Michael J. Moore" <hicamel_at_home.com> wrote in message news:_7Bx5.219701$i5.3017214_at_news1.frmt1.sfba.home.com...Received on Tue Sep 19 2000 - 20:53:19 CDT
> if for example you have a large number of records that you just need to
> store once and then read them sequentially once. We collect sessions from
a
> network, aprox a million per day. These session records are the input to a
> process which looks up additional information based on the content of the
> session record. There does not seem to be any reason to dump these session
> records into a database table just so that we can sequentially processing
> them through the system. Or is there?
>
> The only possible reason I could come up with is maybe, if we had multiple
> CPU's and the table was spread over many disks, that a parallel query
might
> actually be faster than a sequential read of a flat file.
>
> Possible?
>
> Is there sometimes when a good ol' flat file is a better choice than a
> database?
>
> Thought and reflections greatly appreciated.
> thanks,
> Mike
> Not an actual Oracle Certified DBA, but an incredible simulation!
>
>