A large-scale data migration is planned in a DB2 database. How can the Runstats utility be utilized to ensure data integrity and optimize query performance after the migration?
- Implement triggers on the migrated tables to automatically update statistics whenever changes occur
- Manually adjust the query plans for migrated queries to optimize performance
- Run Runstats on all migrated tables and indexes to update statistics and ensure accuracy of optimizer decisions
- Use the Runstats utility to schedule periodic backups of the migrated data to guard against potential data loss or corruption
Running Runstats on migrated tables and indexes updates statistical information, enabling the query optimizer to make informed decisions about query execution plans. This helps maintain data integrity by ensuring accurate statistics reflecting the newly migrated data. Scheduling backups using Runstats does not directly contribute to data integrity or performance optimization but rather aids in data protection. Triggers for updating statistics may introduce unnecessary overhead and complexity, whereas manually adjusting query plans is impractical and error-prone, especially for large-scale migrations.
Loading...
Related Quiz
- In DB2, what is clustering used for?
- What is the purpose of the DB2 Command Line Processor (CLP)?
- How does normalization help in reducing redundancy in a database?
- What role do editions and versions of DB2 play in license management and cost optimization strategies?
- Scenario: During peak hours, several users report slow query performance. How can the DB2 administrator identify the cause and resolve the issue promptly?