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
As we are working on big systems and Maintenance windows are never big enough, It could be an interesting feature to add sorting capabilities at table level at least (may be also index level.?)
Currently tables and/or Indexes are always processed in the same alphabetical order and that's a problem when maintenance window is not long enough to process a single database.
So i think it would be nice to have sorting based at least on table name (or size ?) :
ASC
DESC
RANDOM, so the table are processed in random order, you let the system rebuild indexes that will may be never rebuilt in alpha asc order, in automatic plans (because of log files, tempdb, primary file, not big enough depending on table name sort, etc etc)
WITH ASC & DESC, on manual IndexOptimize (MS SQL compatibility mode upgrade) we can start 2 jobs in // that will process one in ASC order and the other in reverse order, without using @indexes parameters that would be a lot work.
May be also we could have a MAX_DURATION setting (to handle online resumable index rebuild)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
As we are working on big systems and Maintenance windows are never big enough, It could be an interesting feature to add sorting capabilities at table level at least (may be also index level.?)
Currently tables and/or Indexes are always processed in the same alphabetical order and that's a problem when maintenance window is not long enough to process a single database.
So i think it would be nice to have sorting based at least on table name (or size ?) :
WITH ASC & DESC, on manual IndexOptimize (MS SQL compatibility mode upgrade) we can start 2 jobs in // that will process one in ASC order and the other in reverse order, without using @indexes parameters that would be a lot work.
May be also we could have a MAX_DURATION setting (to handle online resumable index rebuild)
Beta Was this translation helpful? Give feedback.
All reactions