AlexSQLForums - Thursday, January 25, 2018 1:36 PM

Grant Fritchey - Thursday, January 25, 2018 12:11 PM

AlexSQLForums - Thursday, January 25, 2018 10:10 AM

Grant Fritchey - Thursday, January 25, 2018 12:11 PM

AlexSQLForums - Thursday, January 25, 2018 10:10 AM

Did you do the following after migration
Use DB;
DBCC UPDATEUSAGE(DB);
GO
EXEC sp_updatestats;
GO

Why would you immediately run sp_updatestats on slow execution of a query? Maybe UPDATE STATISTICS WITH FULLSCAN has already been run. For any table with a single row or more modified, you'll now get a sampled update of the statistics. Without knowing a lot more about the situation, this is actually poor advice.

Did you do the following after migration
Use DB;
DBCC UPDATEUSAGE(DB);
GO
EXEC sp_updatestats;
GO

Why would you immediately run sp_updatestats on slow execution of a query? Maybe UPDATE STATISTICS WITH FULLSCAN has already been run. For any table with a single row or more modified, you'll now get a sampled update of the statistics. Without knowing a lot more about the situation, this is actually poor advice.

I asked if sp_updatestats were executed after the migration and not on slow execution of the query.