Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
HCL OneDB™ extensions and DataBlade® modulesThese topics describe how to use built-in database extensions and separately installed DataBlade® modules.
Spatial Data User's GuideThe HCL OneDB™ Spatial Data User's Guide contains information to assist you in using the HCL® OneDB® spatial extension. The HCL® OneDB® spatial extension adds custom data types and supporting routines to the server.
Estimate your spatial dataThe total amount of space you need for spatial data is equal to the size of spatial tables plus the size of the spatial indexes.
Estimating the storage space for the tableThe total size of a spatial table is equal to the column sizes plus the dbspace overhead size multiplied by the number of rows.
Estimate dbspace overhead requirementsThe amount of dbspace overhead that spatial tables require depends on the number of rows.

Estimate dbspace overhead requirements

The amount of dbspace overhead that spatial tables require depends on the number of rows.

Spatial tables with more than 10,000 rows require about 200 bytes of overhead per row.

Spatial tables with fewer than 10,000 rows but more than 1,000 rows require 300 bytes per row.

Spatial tables with fewer than 1,000 rows require 400 bytes per row.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.