In one of our Microsoft Dynamics 365 for Finance and Operation implementation projects we had the situation, that the fragmentation percentage of some tables were growing up to 99 percent. In the log of the nightly index maintenance run, those indexes always got marked as skipped.
The reason behind was that we were running index maintenance in online mode for 120 minutes. When this job is running in online mode it’s trying to acquire a lock for the index and when the index is constantly in use the job will never get the lock.
The solution in our case was to reschedule some other batch jobs to get a period of 90 minutes during the night where almost nothing runs on the environment. In this 90 minutes we scheduled the index maintenance in offline mode, which now catches all necessary indexes.
What is your index maintenance strategy and are you as excited as me about the new index maintenance capabilities coming with platform update 33?