Sandbox copy can stall on object history table for production organizations with large history tables
Last updated 2016-07-28 ·Reference W-2551955 ·Reported By 2 users
When a large duration of Object History is selected for a Full sandbox copy on a production organization with a very large amount of object history data, sandbox copy can stall on the Object History table. Organizations have encountered this when object history criteria on the sandbox copy settings included History rows in the 60 Million+ count range.
Sandbox copy duration for large organizations can vary for a variety of reasons. Only salesforce support will be able to attribute a specific sandbox copy delay to this issue.
In the rare cases in which copies have been identified to have this issue, the workaround has been to have R&D skip the entity history table. Future copies for impacted organizations should have the lowest possible history setting selected for a full sandbox copy, until the copy architecture has been enhanced to more efficiently parse very large Object History Tables.
In general, customers should choose the minimum duration of object history to include in a full sandbox copy, as the data quantity can be significant, and a major contribution to copy duration timeframes.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.