You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a time limit has been set some indexes or statistics operations could end up running over due to the size and how close to the end of the window the operation starts.
Using the data collected in the CommandLog table we could use this to estimate how long the operation may take and skip processing the object if it exceeds the time limit.
This feature is aimed at SQL < 2017 as the MAX_DURATION setting is available.
The text was updated successfully, but these errors were encountered:
siweston
added a commit
to siweston/sql-server-maintenance-solution
that referenced
this issue
Jun 23, 2022
…ate Command Duration
Update IndexOptimize - Add @TimeLimitEstimateCommandDuration (options: Min,Avg,Max) - Estimate duration of index and statistics commands for an object - skipping if the current time + duration exceeds the time limit. Also remove TimeLimit check around listing indexes in current database otherwise you receive error 'The following objects in the @indexes parameter do not exist' running when exceeded time limit
If a time limit has been set some indexes or statistics operations could end up running over due to the size and how close to the end of the window the operation starts.
Using the data collected in the CommandLog table we could use this to estimate how long the operation may take and skip processing the object if it exceeds the time limit.
This feature is aimed at SQL < 2017 as the MAX_DURATION setting is available.
The text was updated successfully, but these errors were encountered: