Book Image

Applying and Extending Oracle Spatial

Book Image

Applying and Extending Oracle Spatial

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
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Table Comparing Simple Feature Access/SQL and SQL/MM–Spatial
Index

AWR reports


Oracle provides powerful tools for diagnosing database performance bottlenecks, such as long running queries and disk I/O waits. These are Advanced Workload Repository (AWR) and Automated Database Diagnostic Monitor (ADDM) tools. These are very useful tools for understanding how the application level APIs affects how the DB performs. Often times, some application API calls will take more time to complete while a seemingly similar application API call takes much less time to complete, for example, a user's application might be drawing different layers of spatial data on a map. From the application's point of view, there might not be much difference between the different layers of data, but on the database, the underlying queries against the different layers might perform differently. In this section, we describe how to use database supplied tools to collect and analyze information regarding the application workloads.

While analyzing bottlenecks for an application, it is good practice...