
The server components (SMS Server module) of Configuration Manager enter status messages into the database, which can be extracted from the SQL v_StatMsgWithInsStrings view using, for example, the following SQL query:

Using the data collected from a certain instance of Configuration Manager, extracted with the above query, it can be presented in the form of a graph:

Relating the obtained values to the average value, one can see the excessive height of the "bars" representing Saturday data.
Analysis of 'Saturday messages', in terms of components (Component) and message identifiers (MessageID), shows the component service 'SMS_DISTRIBUTION_MANAGER' as the main source. Since I have no mention of errors here, it can be assumed that this service just has a bit more work than usual on Saturdays.
It is quite easy to associate this fact with the default setting of distribution points:

As you can see, the process of checking distribution packets on distribution servers must produce the observed effect. If we have n distribution servers and medium m packets, then the number of additional (above the expected value) messages will be approximately 2*n*m (due to the occurrence of a pair of messages for every packet checked). So, having, for example, 10 distribution servers storing 200 packets each, you can expect to see an additional 4,000 messages (above average), which corresponds quite well to the situation shown in the chart.
- Support and development of Microsoft and Nintex based applications
- Application design and development including digital processes
- Invoice management
- Requisition management
- Contract management
- Modern Intranet
ISCG sp. z o.o.
Al. Jerozolimskie 178, 02-486 Warsaw
NIP: 5262798378
KRS: 0000220621
Phone