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. - Organizing tables by hash for fast access to individual rows
You can organize tables for hash access to improve the performance of queries that use unique equal predicates to access individual rows. - 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 for 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. - Designing indexes for performance
Indexes can provide efficient data access in many situations, and DB2 uses them for other purposes. However, certain costs are also associated with creating and maintaining indexes, and you must consider these costs in your database design.
Parent topic: Managing DB2 performance