Scene:
A table contains two fields (dates, cities)
To save every day push over cities related data table now plan to do the daily amount of data about 300 w partition processing speed up the data query
Currently use date as the primary partition (by day automatically generated partition), cities as a child partition (use the template to automatically generate sub-domain)
But considering cities follow-up will gradually increase how to tune, please?

CodePudding user response:

You are in city as a child, so city increase doesn't really matter

CodePudding user response:

1/f, reference to learning turn response:

you are in city as a child, then the city increase doesn't really matter.

So for partition is generated automatically according to the days of additional sub-domain to primary partition name have to manually check here I don't know I can achieve to all primary partition additional new child partition

CodePudding user response:

Use PLSQL additional, affirmation is not automatically

CodePudding user response:

references to learning turn reply: 3/f

use PLSQL additional, automatic is certainly not

I this person PLSQL is said that PLSQL, use dynamic SQL can reach your demand

CodePudding user response:

Don't know what do you want to add value, how to let Oracle automatically give you add partition?

CodePudding user response:

Reaching + hash master zoning model can be used

CodePudding user response:

Again carefully look at the requirements of the building Lord, I think should first consider the problem is not can automatic partition, but the application of SQL is how to access this list, check of the field is the most frequently? Fine granularity and how? How much is per query involves the amount of data? These problems are should first consider the problem,