Re: Partitioning Best Practices
From: DA Morgan <damorgan_at_psoug.org>
Date: Thu, 10 Jul 2008 15:18:44 -0700
Message-ID: <1215728310.787220@bubbleator.drizzle.com>
>
> Are you sure...? What about SPLIT PARTITION which will add a new
> partition in between existing partitions:
>
> alter table <TABNAME> split partition <MAXVALUE> at <DATE> into
> <NEWPART> , <MAXVALUE>;
Date: Thu, 10 Jul 2008 15:18:44 -0700
Message-ID: <1215728310.787220@bubbleator.drizzle.com>
mccmx_at_hotmail.com wrote:
>> Using a MAXVALUE partition makes it impossible to insert a different >> partition that logically follows the one preceding it: Thus you are >> in a dead-end situation. The best solution is no MAXVALUE and to use >> a regularly scheduled job to add partitions on a regular basis. Make >> sure the job checks for skipped partitions before adding the next one.
>
> Are you sure...? What about SPLIT PARTITION which will add a new
> partition in between existing partitions:
>
> alter table <TABNAME> split partition <MAXVALUE> at <DATE> into
> <NEWPART> , <MAXVALUE>;
I was just referring to ADD.
-- Daniel A. Morgan Oracle Ace Director & Instructor University of Washington damorgan_at_x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Group www.psoug.orgReceived on Thu Jul 10 2008 - 17:18:44 CDT