HELP: Large ORACLE Tables > 3million rows
Date: 1996/04/24
Message-ID: <4ll4fq$qti_at_romeo.logica.co.uk>#1/1
Hello,
I need some help with the design of a system with some large ORACLE tables.
The table will have 100 rows inserted 100 times per day. This will lead to approx 3.5 million rows per year, all of which must be accessible online.
Each row is approx 150 byte, so the table for one year will be approx 500Mb (plus one index of about 50 to 100Mb).
The routine which inserts the 100 records must run quickly and I am worried about the time to update the index.
- Is the index overhead going to be noticeable.
I can split the table so that data over a certain age goes into a history table.
2) How many rows shoudl I keep in my main table before inserts are slowed.
3) If I use a view (UNION ALL so avoid remove distinct rows) to combine the two tables will I get a large performance hit?
I am tendinf towards two tables with the big history table on a separate disk but I do not want to go to this trouble if it is not really necessary.
Many Thanks
Darius Carr (Logica)
All opinions are my own and do not necessarlily refect the opinion of my employers.
Received on Wed Apr 24 1996 - 00:00:00 CEST