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
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: