Re: Oracle Table Spanning

Daniel Morgan wrote:
> Andrey wrote:
>

[...]

> Then please do what has been repeatedly asked ... define "table spanning."
>

better yet, define the original problem that "table spanning" (whatever it means) is supposed to solve?

Sounds like there will still be hundreds of millions of rows stored somewhere, whether in "spanned tables", table partitions or un-partitioned tables.

Is the problem to drop old data regularly without generating unacceptable re-do? Is the problem to improve query performance? Is the problem to perform backups or aggregation with maximum availability? Is the problem to allow custom in-house code to work against the same schema as the ASP's application?

Partitioning can certainly address most if not all of these issues, however 1) it is very expensive (an extra pay on top of Enterprise Edition cost) and 2) changing two tables into a partitions of a single table will almost certainly cause some queries to break, although judicious use of views might work around that.

-Mark Bole Received on Sat Jan 24 2004 - 11:42:07 CST