How does a Db2 pureScale environment compare to a multi-partition database environment?

The IBM® Db2 pureScale Feature, much like a multi-partition database environment, provides a scalable and highly available database solution. However, the instance type and data layout of a Db2 pureScale environment and a multi-partition database environment are different.

Each environment has unique advantages and is tailored for specific types of database processing. Which environment you use depends on your specific business requirements. The following table outlines some of the key differences between a multi-partition database environment and a Db2 pureScale environment.

Table 1. Comparison of a multi-partition database environment and a Db2 pureScale environment
  Multi-partition database environment Db2 pureScale environment
Provides A multi-partition database environment provides members working in parallel in a shared-nothing environment. Data is distributed across partitions, with local access to a subset of data by each member. Typically, a query is processed by multiple members simultaneously. A Db2 pureScale environment provides Db2 members that independently process database requests but access data stored on a shared disk. Each SQL request is executed by a single member.
Designed for
  • Faster response time of long-running or complex queries
  • Management of very large data sets
  • I/O spread across many computers
  • A continuously available database solution
  • Increased throughput of many concurrent short queries
  • Easy scalability
Transaction size and type The ideal scenario for a multi-partition database environment is lengthy workloads that can be subdivided and directed to specific partitions to run in parallel.

A multi-partition database environment is ideal for applications that are part of a decision support system (DSS), for business intelligence applications, and for data warehousing.

 A Db2 pureScale environment is ideal for short transactions where there is little need to parallelize each query. Queries are automatically routed to different members, based on member workload.

The ideal scenario for a Db2 pureScale environment includes workloads that handle online transaction processing (OLTP) or enterprise resource planning (ERP).