DB2 Spatial Extender performance tuning
Configure your spatial database to improve performance
From the developerWorks archives
Date archived: January 12, 2017 | First published: October 06, 2005
In almost every database system it is important to achieve good performance for the workload that is run on the system. With the help of the IBM® DB2® Spatial Extender, spatial data can be seamlessly integrated in your database together with any other data you might want to store. The extender provides a set of data types to represent spatial information. However, the DB2 Universal Database™ (DB2 UDB) database engine does not (yet) know the exact properties of spatial data, and the specialized data types are not (yet) available as built-in types. So tuning your spatial database system towards optimal performance requires a few considerations above and beyond the usual tuning steps you take for other DB2 databases. This article introduces and explains in detail the basic optimization steps that you should consider when working with spatial information.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.