I am moving data from a few billion records table to newly created partitions. I am inserting into the child table directly and deleting from the main table with filters on the appropriate columns in the parent table. Each iteration will move many millions of records. As the stats for the parent table is undergoing significant change because of the deletion, I thought it makes sense to analyze it after each iteration. That way, the insert/delete for the next iteration will go through quickly. But that results in the child tables also getting analyzed, and takes a lot of time. Is there a way to analyze the parent table alone?
Take the 2-minute tour
×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
|
|
