Partitioning strategy Help

[diepa]

I will have several tables with 6,000,000 rows in my database. As an example, this is one of the tables:
TABLE_BIG
FIELD1_PK NUMBER(10)
FIELD2 NUMBER(10)
FIELD3 VARCHAR2(256)
CERATEDATE DATE

Our queries are going to be over the field FIELD1_PK on the where clause and that number is generated using a sequence. That table will start with 5M rows, and will increase with 3M rows/month.
My question is the type of partition that I should use considering that if I have 2 partitions, all of The new values will go to the right side of the partition.
Should I use hash partition over that field? not partition at all?

Thanks,
Diego

 

[Wonboodoo]

If it's a primary key I'm sure it has an index. That's all you need. Partitions are overrated, for most cases indexes are all you need.