Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IndexOptimize - Feature to estimate duration for completing index or statistics operations if a time limit is set and skip if exceeds #653

Open
siweston opened this issue Jun 23, 2022 · 0 comments

Comments

@siweston
Copy link

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.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants