Path: news.f.de.plusline.net!news-fra1.dfn.de!newsfeed.hanau.net!newsfeed2.scan-plus.net!news.germany.com!postnews.google.com!s48g2000cws.googlegroups.com!not-for-mail
From: hasta_l3@hotmail.com
Newsgroups: comp.databases.oracle.misc
Subject: Partitioning examples (was Re: move a row from table t1 to t2)
Followup-To: comp.databases.oracle.misc
Date: 2 Feb 2007 08:56:31 -0800
Organization: http://groups.google.com
Lines: 34
Message-ID: <1170435391.044151.215140@s48g2000cws.googlegroups.com>
References: <1170343560.742415.202130@a34g2000cwb.googlegroups.com>
   <Xns98CA5292CE975anacedenthotmailcom@69.28.173.184>
   <1170346209.864715.221880@q2g2000cwa.googlegroups.com>
   <Xns98CABE83B40A3anacedenthotmailcom@69.28.173.184>
NNTP-Posting-Host: 85.234.196.53
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1170435396 23324 127.0.0.1 (2 Feb 2007 16:56:36 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 2 Feb 2007 16:56:36 +0000 (UTC)
In-Reply-To: <Xns98CABE83B40A3anacedenthotmailcom@69.28.173.184>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: s48g2000cws.googlegroups.com; posting-host=85.234.196.53;
   posting-account=IKOHxgwAAADFMMZsoxvSQipqOS6S45qr
Xref: news.f.de.plusline.net comp.databases.oracle.misc:77898

On 2 f=E9v, 03:43, "Ana C. Dent" <anaced...@hotmail.com> wrote:
> "Prasath" <prasath....@gmail.com> wrote in news:1170346209.864715.221880
> @q2g2000cwa.googlegroups.com:
>
> >Tablet2is used to stored aged data.  Hence, using view is not the
> > solution I am looking for.
>
> Just use partitioning &movethe partition from current_table to
> archived_table

Ana, would you (or anybody else :-) have a reference to a
web site or book with examples of partionning in actual
applications ?

In my case :

1=2E Data have both a creation and an expiry date. Expiry date
is computed and may change (rarely). Different rows have
pretty different (expiry - creation) delays. Ideally,  expiry
date should be used for aging out.

2=2E Partition maintenance shall be transparent to the
user. There is no dba on site.

I would like to study how people implement this kind of
requirements...

Thanks much

--- Raoul