Introducing Netezza Native Cloud Object Storage (NCOS) support

This powerful new capability allows users to create user tables in Netezza data format on S3-compatible object storage, unlocking a new tier of scalability, flexibility and cost-efficiency.

This enhancement is more than just a technical upgrade; it’s a strategic shift that positions Netezza to fully leverage the benefits of cloud-native architectures. By integrating object storage natively, Netezza enables:

• Massive scalability: Object storage can grow virtually without limits, making it ideal for big data workloads.
• Cost-effectiveness: Lower storage costs compared to traditional block storage.
• Data sharing and reduplication: Easier collaboration and reduced redundancy.
• Enhanced durability and resilience: Built-in fault tolerance across cloud regions.

This new capability complements Netezza’s existing block storage support, forming a hybrid storage hierarchy. Users can now transition workloads from block to object storage seamlessly, enabling a smoother migration path to cloud-native deployments.

This hybrid model is a game-changer for customers looking to optimize performance and cost while modernizing their data infrastructure.

Netezza is currently available on leading cloud platforms such as AWS and Azure as SaaS and Bring Your Own Cloud (BYOC) offerings. These public cloud platforms provide object storage that is cheap, scalable and highly capable. For example, AWS S3 is a popular object storage service that can be deployed through an AWS cloud account and scales extremely well while keeping the cost minimal. It is also possible to configure the storage buckets for versioning, redundancy and access control.

With the hybrid storage approach, customers can optionally specify the storage type for a table during creation. If no storage type is defined in the DDL, Netezza automatically selects one based on the database’s default settings or the default system configuration, which are configurable.

Netezza continues to be built upon the concepts of distributed computing and MPP architecture. 

The storage type is opaque to the NPS front-end. Which means that the user should be able to query the tables and join them without worrying about the underlying storage type.

Netezza offers object storage while continuing to support block storage to facilitate transitioning data and workloads from block storage to object storage. Once the object storage is configured, the customer can choose the storage type of the newly created tables. Data can be copied as required between object storage and block storage using simple SQL.

The users should create a separate bucket for each NPS instance. 

Each object stored in the object store follows a structured prefix format:

 “/nps/<instance name>/<dbuuid>/<dsid>”.

The object storage contains objects corresponding to the tables and metadata. Each data slice has its own metadata objects. The metadata is stored in a large buffer to improve the IO latency.

In Netezza’s object storage architecture, obsolete objects, such as those resulting from dropped, truncated or groomed tables, are tracked using a delete list object. This list is generated during those operations. Then, an asynchronous garbage cleaner is responsible for performing the actual deletion of those objects from the object store.

This means Netezza automatically handles cleanup in the background, ensuring efficient storage management without requiring manual intervention.

To enhance performance and reduce operational costs, Netezza’s object storage leverages local caching. This caching layer delivers low latency and high throughput. A custom caching implementation was developed specifically for the Netezza storage engine, allowing rapid iteration and tight integration with Netezza-specific architecture.

Netezza’s native object storage integration brings powerful benefits to users—without disrupting existing workflows or applications. Here are the key advantages:

1. No changes to customer applications: Applications built for block storage tables continue to work seamlessly with object storage tables; no code changes or reconfiguration required.
2. Full SQL compatibility: All Netezza SQL syntax, tools, and operational features work identically with object storage tables; users experience consistent behavior across both storage types.
3. Improved scalability: Leverages cloud object storage’s inherent scalability for both capacity and IOPS; ideal for growing workloads and large dataset.
4. Transparent cost model: Users are billed based on actual usage—storage volume and API calls; enables better cost control and predictability.
5. Optimized price and performance over time: Netezza employs techniques like high performance local caching and batch writes to reduce API overhead. These optimizations help deliver better performance at lower operational cost, especially for read-heavy and analytical workloads.

To assess the efficiency and reliability of object storage, a diverse set of workloads was executed including read-only queries, mixed analytical operations, write-intensive tasks, and concurrent multi-user scenarios.

Main highlights:

• Performance parity with block storage: Object storage demonstrated comparable performance to traditional block storage across diverse workload types.
• Faster batch write performance: Write-heavy operations, especially batch inserts, showed improved throughput thanks to optimized caching and write strategies.
• Lower storage costs over time: The total cost of running these workloads including API usage was consistently lower on object storage compared to block storage, making it a more cost-effective solution for long-term data management.

To support native object storage, Netezza introduces the storagetype keyword, allowing users to specify the desired storage type at various levels of configuration.

1.   Storage type resolution hierarchy: If table level is specified in the CREATE TABLE statement, the table uses the defined storage type.

2.  Example: CREATE TABLE t1 (c1 INT) storagetype ‘object’;Session-Level:  If not specified at the table level, the storage type is inherited from the session. Example:

               SET default_storage_type = ‘object’;

               CREATE TABLE t1 (c1 INT)

3. Database-Level: If not specified at the session level, the storage type is inherited from the database. Example:

CREATE DATABASE db1 storagetype ‘object’;

ALTER DATABASE db1 storagetype ‘object’;

4. Global Setting: If not specified at the database level either, the system falls back to the global default storage type set in system configuration. Example:

SET default_storage_type = ‘object’;

This hierarchy ensures flexibility while maintaining consistency across deployments.

Native Cloud Object Storage for Netezza on AWS is now available in public preview, with General Availability planned for AWS and Azure in Q42025.

Netezza now supports native cloud object storage, enabling users to create and manage tables directly on S3-compatible cloud storage. This hybrid model combining block and object storage offers better scalability, lower costs and seamless SQL compatibility.

With caching, asynchronous cleanup and flexible storage configuration via the storagetype keyword, Netezza delivers improved price-performance while maintaining a consistent user experience. Netezza NCOS public preview is a solid foundation to spur a wave of new capabilities that will excite our users. 

We recommend users to explore object storage by running their workloads and determine the best balance for their data and workload needs.

Explore today