SOE data from SQLT history tables

Hi Colby,

I have looked into database partitioning before. Postgres supports partitioning through inheritance. Basically you create a master table (which stays empty) and a number of child tables. Each child table will have a constraint that limits new data to a range (usually a date) for that partition. It gets more complex because you have to create the child table and modify the constraint for each of them. As I said, if this was a production system I’d be looking into this sort of thing.

Mysql partitioning is still fairly new. (I think it was interduced in ver 5)

It’s also the sort of thing that you really want a DBA on hand to help set up.(cause you just tell him to do it and not worry about it :smiley: )

For more information see:
Postgres
Mysql