See the best practices to design and implement scalable solutions that facilitate the continuous feed or roll-in and roll-out of data, with minimal interruption of data access.
Today’s database applications frequently require scalability and rapid
roll-in and roll-out of data with minimal disruption to data access by applications. Roll-in of data refers to the addition of new data as it becomes available while roll-out of data refers to the moving out (usually archiving) of historic data. Many applications today are accessed 24
X 7, therefore eliminating the previously available batch window for data updates. Also, many applications require the continuous feed of data updates while applications concurrently access the data.
The DB2 database system provides a variety of facilities that enable scalability and facilitate the continuous feed or roll-in and roll-out of data, with minimal interruption of data access. This document recommends best practices to design and implement these DB2 facilities to achieve these goals.
- Executive Summary
- Introduction
- Partitioning techniques
- What is database partitioning?
- What is table partitioning?
- Multi-dimensional clustering
- Features of MDC that benefit roll-in and roll-out of data
-
Using database partitioning, table partitioning and multi-dimensional clustering in the same database design
- Additional techniques to support life cycle management
- Large table spaces
- SET INTEGRITY operation
- Asynchronous index cleanup
-
Designing and implementing your table partitioning strategy
- Design best practices
- Maximizing the benefits of partition elimination
- Operational considerations
- Rolling in data: Which solution to use?
-
Best practices for roll-in of compressed table partitions
- Best practice for roll-in and roll-out with continuous updates
- After roll-out: How to manage data growth and retention?
- Using UNION ALL view
- Using IBM Optim Data Growth Solution
- Best Practices
- Conclusion
- Further Reading
- Notices
"
Data Life Cycle
Management
"
(October 2009)
See the best practices to design and implement scalable solutions that facilitate the continuous feed or roll-in and roll-out of data, with minimal interruption of data access. (pdf; 681KB; 33 pages)
Comment, edit, or add your own insights to the Deep Compression best practices
on the IBM Database Wiki
Check out all the other Best Practices papers and see how you can improve your experience with DB2 for Linux, UNIX, and Windows.
| 
