Skip to content

dbo.IndexOptimize performance feature #909

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

Open
karobe00 opened this issue Mar 17, 2025 · 0 comments
Open

dbo.IndexOptimize performance feature #909

karobe00 opened this issue Mar 17, 2025 · 0 comments

Comments

@karobe00
Copy link

First off, thank you for all of your hard work on this and providing this solution! Great Job!

On large (3TB+) databases with high loads, the function, sys.dm_db_index_physical_stats() called in dbo.IndexOptimize can take a long time to return fragmentation levels. On a few of our systems, I have seen it take our entire 2 hour maintenance window.

The feature I am requesting is the ability to run the dbo.IndexOptimize to identify what needs to be done and then again with a different switch to do the actual index defrags/rebuilds. this would allow us to schedule a time to figure out fragmentation, which does not typically cause blocking, a few times a week and then have a different schedule for defrags/rebuilds during our daily maintenance window.

We were considering using the combo of LogToTable = 'Y' and Execute = 'N' to write to the log table and use that as a "work" table, but we are switching to these scripts to conform to industry standards and we don't want to add custom code that could break with new releases of dbo.IndexOptimize.

I really appreciate any support you are able to provide. Thanks!

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