Skip to Content
Sep 14, 2016 at 05:45 AM

Data Partitioning Strategy



I have scenario here , i have 3 tables and i am anticipating they are going to grow in large size possibly over 2 billion records in future.

The application using these tables is yet to be deployed , i am looking here strategy for partitioning the table.

Do i create partition for these tables after the application is deployed for production and seeing the growth rate of table data ( monitoring some threshold limit of no of records which i am not aware of now) or do i design partitions for tables in schema before i deploy this into production?

If i have to partition can i partition on Range partitioning on timestamp column, ? on month or on year vale of timestamp?

many thanks