Migration Challenge: Excessive FULLSCAN Statistics Update Duration Blocking SQL

  • Hello everyone ,

    I am planning to migrate a database from SQL Server 2014 to SQL Server 2019. The migration process includes a double-run, and one of the steps in the timeline is an UPDATE STATISTICS with FULLSCAN.

    This operation takes more than three days, which makes the cutover impossible because such a delay is not acceptable.

    I would like to know whether this step can be skipped, or if there is a way to optimize or replace it. My concern is that skipping it may lead to poor execution plans after the migration

    Thanks

Viewing post 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply