The total number of queued data discovery records (DDRs) on the site server has exceeded the standard operational threshold. This condition increases unless it is resolved. If the queued site server DDR count continues beyond the threshold, discovered information is not reflected in the Configuration Manager site database in a timely manner, and collections and reports might not accurately represent the devices on the network.
The total number of queued DDRs can exceed the threshold because:
The SMS_Executive service is stopped or not responding on the site server.
Discovery Data Manager could be processing changes to site boundaries or the parent site, or it could be sending inventory details to a new parent site. These changes take priority over regular DDR processing, which is suspended until they are processed.
The site server DDR processing rate is slower than the DDR incoming rate.
The site server has insufficient resources, such as CPU, memory, or disk space.
The Configuration Manager site database has no more space.
A large number of clients has recently been discovered.
The site server might have lost connectivity to the Configuration Manager site database server.
To resolve this issue and lower the number of queued DDR files:
Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific Configuration Manager site.
Verify that the SMS_Executive service is running on the site server. If it is stopped or not responding, restart the service.
Verify that the Configuration Manager site database is performing properly.
Determine whether the increased load is due to an infrequent influx of new data discovery records, or whether the DDR load remains relatively constant. If the load is constant, update the Configuration Manager infrastructure to achieve zero processing backlogs. If the load is due to a large number of newly discovered client computers, the issue might resolve itself if there are sufficient resources to process pending DDRs in addition to the standard DDR load.
Verify that the Configuration Manager site database has sufficient space. If the database is set to autogrow, verify that there is sufficient disk space for the database to expand.
Plan the type and frequency of your discovery methods carefully. Conduct performance testing to verify that the infrastructure can accommodate the discovery load. Adjust the frequency of discovery to allow for a longer interval for DDRs to be processed.
Modify the discovery configuration to discover fewer resources.
Verify that the site server can connect to the Configuration Manager site database server.
For more information about server sizing, see Planning and Deploying the Server Infrastructure for Configuration Manager 2007 in the Configuration Manager Product Documentation Web page.
For more assistance, see the list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager.