Quick question.
One of the DBA has a SQL Agent Job that runs on weekends that looks at indexes, and if there is 30% or more fragmentation, the indexes are dropped and recreated.
On the other hand, as I explore the various issues we have with performance, I am seeing articles that indicate several solutions, including running sp_updatestats to update the statistics in the query plans. The recommendation is to turn off automatic updates and run a nightly manual job using sp_updatestats.
I am being told by the other DBA that this (sp_updatestats) would not be necessary because the stats are updated on those tables where the index is rebuilt during the weekend.
Is this true? We are running SQL Server 2005 with sp2 in our production environment.
Glen Braden
One of the DBA has a SQL Agent Job that runs on weekends that looks at indexes, and if there is 30% or more fragmentation, the indexes are dropped and recreated.
On the other hand, as I explore the various issues we have with performance, I am seeing articles that indicate several solutions, including running sp_updatestats to update the statistics in the query plans. The recommendation is to turn off automatic updates and run a nightly manual job using sp_updatestats.
I am being told by the other DBA that this (sp_updatestats) would not be necessary because the stats are updated on those tables where the index is rebuilt during the weekend.
Is this true? We are running SQL Server 2005 with sp2 in our production environment.
Glen Braden