Functionality in Db2 product editions
With Db2®, all editions have the same code base. The technical differences among editions are resource limitations functionality advanced features or tool sets. In this way, applications that are written for any Db2 edition can be moved easily to any other Db2 edition, on any operating system platform that is supported by Db2.
Table 1 lists the functionality available in each. Db2 12.1 product edition.
Functionality | Db2 Community Edition | Db2 Starter Edition | Db2 Standard Edition | Db2 Advanced Edition | Db2 Warehouse |
---|---|---|---|---|---|
Product type | Free | Paid | Paid | Paid | Paid |
Workload type | Transactional and analytics1 | Transactional and analytics1 | Transactional and analytics1 | Transactional and analytics | Analytics |
Capacity restrictions | Maximum of 4 processor cores and 8 GB of memory on each physical or virtual server | Maximum of 4 processor cores and 16 GB of memory on each physical or virtual server | Maximum of 16 processor cores and 128 GB of memory on each physical or virtual server | None | None |
Prohibited functionality | The following functionality is prohibited:
|
Following functionality is prohibited:
|
Following functionality is prohibited:
|
None | Following functionality is prohibited:
|
Support availability | Community support | Paid enterprise support | Paid enterprise support | Paid enterprise support | Paid enterprise support |
License metrics | None | Virtual Processor Core (VPC)3 | Virtual Processor Core (VPC)3Authorized User (AU)4 | Virtual Processor Core (VPC)3Authorized User (AU)4 | Virtual Processor Core (VPC)3 |
1 For analytics workloads, only single-node deployments are permitted.
2 For native encryption, applies to both database and backup encryption.
3, 4 Refer to the license documents of the respective product edition for metric definition. The VPC metric can be used for both production and non-production environments. The AU metric can only be used for non-production environments.