Gatherings are slow within Messagestats.
There are various reasons why a gathering may be slow, large environments, below-optimal connection speeds, other resource heavy applications running such as backup software or antivirus, initial misconfiguration, lack of task execution servers, network bumps, gatherings not based upon regions, gatherings with sources as regions and not servers, Using a remote Database Server, etc. This article is to be used as a possible workaround for such issues and not as an absolute solution for such,
Potential Resolutions
Free up system resources by removing other resource intensive applications.
Make sure the SQL Server MessageStats uses is on the same network segment as all of your task processors.
In very large environments you can add additional task processors to spread out you gathering.
The Messagestats gathering structure can be customized to gather information independent of the Default Gathering,
Needed order of gatherings. This is important, where as deviating from this order will result in hung sub-tasks.
Exchange Organization Structure
Exchange Custom Recipients
Exchange Server Properties
Exchange Virtual Servers
ExchangeInternal Name Spaces
Exchange Connectors
Exchange Distribution Lists
Exchange Information Stores
Exchange Mailbox
Exchange Mailbox
Exchange Mailbox
Exchange Mailbox
Exchange Tracking Logs
Note:
30 minute or 1 hour spacing should be fine, it could be tweaked or adjusted if need be.
This was initiated and proven in two large environment cases.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center