Re: Table Design

Hi Diego,

(1) Take a look at the Oracle Documentation where "partitions" (range partitions) are described. Range partitions would enable you to also easily maintain (delete/move/takeoffline) your data. Think of good partition keys when desining your table.
(2) Do not use LONG, LONG RAW datatypes (they are limited and support I think will be stopped in the next future). Use CLOB, BLOB, etc. instead. (3) There is no general concept for storage parameters, indexes, database parameters (that depends on your specific needs). That's why it's configureable ;-) - But in most cases it's an exercise of mathematics - take a look at the rows data and it's types (be careful VARCHAR, CHAR etc.) - and then make your decision. Also try to avoid fragmentation.

Walter

"Diego" <dpafumi_at_yahoo.com> wrote in message news:5b2b7013.0107150904.7104a791_at_posting.google.com...
> Hi,
> I need to design a database (not DW). This DB will contain a big
> tables (with 500.000 insert and several updates over those rows) per
> day.
> Basically, we are going to insert a lot of data (about 50K rows), then
> we will start "working" with that data doing updates (not deletes at
> all) over that table and other tables. In the meantime we will
> continue with the inserts over that table to arrive to 500K rows.
> So we are going to generate 500,000 rows per day, at the end of the
> date we are going to delete that data or send it to another place, so
> at the beginning of the next date the table will be empty.
>
> Can anybody suggest me the best way to design those tables (storage
> parameters and type of table), indexes and the database parameters?
> Any suggestions?
> I would consider partition for that big table, I'm ok?
> Thanks
> Diego
Received on Sun Jul 15 2001 - 13:09:56 CDT