Book Image

Applying and Extending Oracle Spatial

By : Siva Ravada, Simon Greener
Book Image

Applying and Extending Oracle Spatial

By: Siva Ravada, Simon Greener

Overview of this book

Spatial applications should be developed in the same way that users develop other database applications: by starting with an integrated data model in which the SDO_GEOMETRY objects are just another attribute describing entities and by using as many of the database features as possible for managing the data. If a task can be done using a database feature like replication, then it should be done using the standard replication technology instead of inventing a new procedure for replicating spatial data. Sometimes solving a business problem using a PL/SQL function can be more powerful, accessible, and easier to use than trying to use external software. Because Oracle Spatial's offerings are standards compliant, this book shows you how Oracle Spatial technology can be used to build cross-vendor database solutions. Applying and Extending Oracle Spatial shows you the clever things that can be done not just with Oracle Spatial on its own, but in combination with other database technologies. This is a great resource book that will convince you to purchase other Oracle technology books on non-spatial specialist technologies because you will finally see that "spatial is not special: it is a small, fun, and clever part of a much larger whole".
Table of Contents (20 chapters)
Applying and Extending Oracle Spatial
About the Authors
About the Reviewers
Table Comparing Simple Feature Access/SQL and SQL/MM–Spatial

High performance loading

Next, we show a very useful trick to add large volumes of new data to an existing partitioned table already indexed. We want to add this data in such a way as to avoid disruption to queries against the table, and at the same time, reduce the cost of index maintenance on the partitioned table. There are two cases we can consider. In the first case, the new data that is coming in does not have to be available for queries as soon as the data is acquired. This can be supported with a staging table to collect the incoming data. In the second case, the incoming data should be available for queries as soon as the data is acquired. In this case, we cannot use a staging table and the data has to be directly inserted into the base table.

Loading with a staging table

In this case, the data is coming in at a very fast rate or is being moved from an OLTP database to a data warehouse. In both cases, we can use a staging table to collect the incoming data so that the index on the...