Designing databases for performance

You can implement certain database design elements to improve Db2 performance, especially in special situations.

Choosing data page sizes
Db2 provides many options for data page sizes.
Designing databases for concurrency
By following general recommendations and best practices for database design you can ensure improved concurrency on your Db2 system.
Managing space and page size for hash-organized tables (deprecated)
By managing the table space size of your hash-organized tables you can reduce the cost of accessing the index for rows that overflow the fixed hash space. Hash-organized table spaces are deprecated and likely to be unsupported in the future.
Using materialized query tables to improve SQL performance
Materialized query tables can simplify query processing, greatly improve the performance of dynamic SQL queries, and are particularly effective in data warehousing applications, where you can use them to avoid costly aggregations and joins against large fact tables.
Improving performance for LOB data
You can improve the performance of applications that access LOB data by specifying that an inline portion of LOB data columns be stored in the base table space along with data from the other non-LOB columns.
Choosing data page sizes for LOB data
Choosing a data page size for LOBs (in the LOB table space) is a trade-off between minimizing the number of getpage operations (maximizing performance) and not wasting space.
Reserving free space in table spaces
By reserving free space in table spaces you can enable your data to remain clustered longer between reorganizations and you can reduce the number of indirect references and overflow records, which can harm performance.
Compressing your data
You can reduce the space required for a table by using data compression. Compressing the data in a table space can significantly reduce the amount of disk space that is needed to store data and can help improve buffer pool performance.
Increasing free space for compressed data
You can provide free space to avoid the potential problem of more getpage and lock requests for compressed data.
Determining the effectiveness of compression
Determine the effectiveness of your compressed data by learning how much space can be saved and how much processing the compression of your data requires. Analyzing compression effectiveness can help you decide if the performance overhead of compression is worth the space savings.

Parent topic: Managing Db2 performance

Related concepts

Implementing your database design
Altering your database design

Related information

Designing and implementing Db2 databases