RE: Database Outages - Best Practices

When I used V7 we had tables for each year of data and then used a view
to present the data
to the user. It was easy to delete a years worth of data, Just change
the view. Of course it
did not act like partitioning does when a request for data was made.
But it did allow for ease
in maintenance and backups.
Ron

>>> "Hollis, Les" <Les.Hollis@xxxxxx> 02/17/2005 9:54:24 AM >>>
That would be great IF the client were to pop the bucks for
partitioning.

PLUS this is a V7 database I'm talking about here specifically....PLUS
it is Oracle Financials which you don't want to muck around with table
definition's, etc...AOL doesn't like it  PLUS....PLUS......

You have a pretty good understanding of that part of
partitioning...but
AGAIN, it is expensive and not all customers/clients are willing to
pay
the price

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx 
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of david wendelken
Sent: Thursday, February 17, 2005 8:30 AM
To: oracle-l@xxxxxxxxxxxxx 
Subject: RE: Database Outages - Best Practices

>> Table reorgs  (Typically after huge deletes as in a table purge..)

>> ...So you purge data, drop a table from 27G to 16G , ...


Aren't huge deletes like this forseeable when the system is built?

If so, couldn't the tables be partitioned according to the criteria
for
deletion - such as accounting period, etc.?

I know - not always!=20

But where it could be, the downtime wouldn't be needed at all, would
it?

Just drop the partition and be done with it.  Or have I misunderstood
how partitions work?


--
http://www.freelists.org/webpage/oracle-l 

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l

Other related posts: