 |
Experts on Demand
We have a tablespace partitioned by year. The last partition was defined many years ago for the year 2004. The app behind this tablespace is going away in the near future so I'm just letting 2005 data load into the 2004 partition. Do you see any problems with this lazy approach?
QUESTION POSED ON: 09 FEB 2005
QUESTION ANSWERED BY: Craig Mullins, Years 2005-2006
This "lazy" approach is probably your best course of action right now and I'd probably do the same thing. I guess the potential areas of trouble that could come up would include:
- The last partition becoming a hot spot based on how the data is accessed.
- Space or sizing issues; that is, the last partition running out of space before the application is retired
- If you reorganize by partition and expect each partition to take about the same amount of time, then the longer you put more data into that last partition, the greater the chance that the reorg time for that partition will exceed your maintenance window.
- The application living longer than you expected so that 1, 2 and/or 3 above become more likely
Good luck, and do whatever you can to accelerate the demise of that application.
|
|
|
|
|
|
|
|
| TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of . |
|
| |
All Rights Reserved, , TechTarget |
|
|
|
|
|
