MySQL Forums
Forum List  »  Partitioning

Re: Auto Partitioning using unix time
Posted by: Mikael Ronström
Date: March 08, 2006 01:43AM

JinNo Kim wrote:
> Is the event feature an anticipated replacement
> for
> the auto generation of new partitions, or is it a
>
> suggested work around? I ask specifically because
>
> I've been toying with migrating our existing 5.5
> billion row dataset to a partitioned solution and
>
> recently received a new requirement for approx 4.5
>
> billion rows of storage (short term - data import
>
> is occurring now on 4.1, different schema from
> the previous project).
>

The new EVENT mechanism is designed for handling all
types of event-driven requirements. The original request
from you to integrate partition growth at insert where no
partition exists to insert into is a bit more than this.
However I hope that this EVENT mechanism should be
sufficiently advanced to serve your needs. Please let us
know if this is not the case and what is missing in that
case.

Rgrds Mikael

> Based upon our current disk capacity and the data
>
> rates, I expect to be in the ~20 billion row range
>
> in ~6 months (10 billion existing + ~45
> million/day new records). I haven't bothered to
> figure out when we'll be out of space - that's
> coming soon.
>
> ^
> | _explains my recent absence from the boards
>
>
> Just asking for a little clarification (I know
> the reqs for auto-part have not yet been
> submitted - sorry, my bad been very occupied
> recently).
>
> -JNK

Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog: http://mikaelronstrom.blogspot.com

Options: ReplyQuote


Subject
Views
Written By
Posted
7430
January 17, 2006 03:14PM
3415
January 30, 2006 07:09AM
2900
January 31, 2006 08:06AM
2629
February 10, 2006 11:22PM
2698
March 07, 2006 08:00AM
Re: Auto Partitioning using unix time
3034
March 08, 2006 01:43AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.