Storage hierarchy in Native Cloud Object Storage

Native Cloud Object Storage (NCOS) experience in Db2 Warehouse

The Native Cloud Object Storage (NCOS) support on Db2® Warehouse on provides a simple path for adoption through its direct integration within the existing storage hierarchy of Db2, allowing existing applications to leverage the low-cost object storage for Db2 tables without changes.

To create a table stored in object storage, users will follow the existing process of creating a table in Db2 Warehouse. Tables are created within a storage hierarchy that includes the object created in a table space, and the table space is associated with a storage group. The main difference introduced by the NCOS feature is in the definition of the storage group. A storage group will now be defined as associated with a storage access alias instead of being associated with a set of storage paths. The storage access alias designates the storage group as persisting to object storage, or a 'remote' storage group.

Any tablespace linked to a remote storage group will be stored within the storage infrastructure defined by the storage access alias assigned to the storage group. These are referred to as remote tablespaces. Similarly, database objects such as tables, indexes, or materialized query tables (MQTs) associated with these remote tablespaces will reside in the same object storage target, benefiting from the performance optimizations provided by the multi-tiered caching architecture.