Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: DistMgr is slow to process .pul files from pull DPs in System Center Configuration Manager version 1511

FIX: DistMgr is slow to process .pul files from pull DPs in System Center Configuration Manager version 1511

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You're running Microsoft System Center Configuration Manager version 1511.
  • You create a large number of packages (for example, several hundred) and distribute them to lots of pull distribution points (for example, thousands of them).

When DistMgr processes .pul files from the pull distribution points (DPs) in this scenario, DistMgr runs the following query, which takes 3–4 seconds to run when there are many rows in the PkgStatus table:

select s.ID, s.PkgServer, s.SiteCode, p.StoredPkgVersion, s.Status, r.PkgVersion, r.ActionState, r.ActionData, p.PkgFlags, p.ShareType 
from PullDPResponse r 
join PkgStatus s on r.PkgStatusID = s.PKID AND r.PkgStatusID = PUL_ID 
join SMSPackages p on s.ID = p.PkgID

↑ Back to the top

Cause

This issue occurs because the PkgStatus view uses an ISNULL statement, and this causes SQL to perform an Index Scan instead of an Index Seek.

↑ Back to the top

Resolution

After you apply this hotfix, and DistMgr processes .pul files from the pull DPs, DistMgr runs the following query, which takes about 28 milliseconds to run:

select s.ID, s.PkgServer, s.SiteCode, p.StoredPkgVersion, s.Status, r.PkgVersion, r.ActionState, r.ActionData, p.PkgFlags, p.ShareType 
from PkgStatus2 s 
join PullDPResponse r on r.PkgStatusID = s.PKID AND s.PKID = 72057594038363660 
join SMSPackages p on s.ID = p.PkgID

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have System Center Configuration Manager version 1511 installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform
Update.sqlNot Applicable2,04624-Nov-201501:00Not Applicable

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbautohotfix, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb, SCCM, ConfigMgrCB

↑ Back to the top

Article Info
Article ID : 3101706
Revision : 3
Created on : 9/19/2017
Published on : 9/19/2017
Exists online : False
Views : 319