"Brian Peasland" <oracle_dba_at_peasland.com> wrote in message
news:3E394EF0.457BCA63_at_peasland.com...
> > I think the most significant strategic point
> > is that a database of this sort is almost
> > always susceptible to partitioning, with
> > a date-based partition. So a large fraction
> > of the database can be put into read-only
> > tablespaces.
>
> Unfortunately, we are not talking about date-based data here. What we
> have is spatial data in this database. For instance, I have one group of
> tables that holds elevation data for the entire Continental U.S. This
> group of tables is 50GB in size. While data doesn't get updated on a
> daily basis, updates are applied once every two months.
Just wondering if partitioning the data on some geographic/spatial
coordinate basis will help then (presumably mount rushmore isn't moving too
fast :( ). Whilst this won't get you read only tablespaces it might get you
logical units of backup that can be backed up in parallel to multiple
drives?
--
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Thu Jan 30 2003 - 11:37:14 CST
