Re: Info on large tables wanted

Thank you for this link!

I have not yet decided on what Hardware it is going to be run, i will collect further information first. I think that i can compact the data on a half-hourly basis, as they only need to know how many pretzels they sell between 10:00 and 10:30 for example, this gives quite small tables. But it would be quite interesting for them to have a complete sales Journal for future expansions. I think i will store the raw data in a seperate tablespace and generate compacted data from the raw data as well to be stored in a much smaller table for the actual reporting.

MV

• Original Message ----- From: "Romeo Olympia" <rolympia_at_hotmail.com> Newsgroups: comp.databases.oracle.server Sent: Monday, June 07, 2004 5:00 AM Subject: Re: Info on large tables wanted

> 36 million records (or even 150 million) isn't really that big a
> number. The structure even suggests that your average row length is
> quite well.. average. Of course it would help if we know your hardware
> capacity beforehand (number of CPUs, disk configuration, and memory
> which you already provided).
>
> Your system is probably not a dedicated data warehouse but look up the
> Data Warehousing Guide for Oracle. The link below is for 9i; find the
> one for your specific version (hopefully you have at least 8i).
>
> Oracle9i Data Warehousing Guide
> Release 2 (9.2)
> Part Number A96520-01
>

http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96520/toc.htm
>
> This document will introduce you to the different methods of handling
> "large" data in Oracle. Things to pay attention to (not exhaustive):
> - Partitioning
> - Parallelization
> - Bitmap indexes (if applicable)
> - etc.
>
> Hope that helps.
>
> Romeo
Received on Mon Jun 07 2004 - 01:08:59 CDT