Collections Configuration Manager-a can be updated on demand ("manually"), through a schedule or incrementally. The latter method seems very sympathetic, as the default time "proposed" by the system is 7 days. With a larger number of collections, however, this interesting mechanism can be troublesome, leading to a loop in the operation of the component service SMS_COLLECTION_EVALUATOR. This manifests itself in hourglasses remaining for a long time next to the collection icons in the admin console.
According to the company's recommendations Microsoft we should exercise restraint in the incremental updating of collections, not exceeding the contractual limit of 200. However, how do we check how many collections actually use this updating mechanism, bearing in mind that it is also possible that there is a parallel updating through the scheduler?
An SQL query will come to the rescue here:
The result is information about the number of collections that are not updated, have update by schedule, are updated incrementally, or both incrementally and by schedule. The sum of the latter two numbers should not exceed 200.