Consider the following scenario. A manager has thousands of direct reports. When you perform a profile import in Microsoft Office SharePoint Server 2007, many colleagues are auto-populated from the organization hierarchy. In this scenario, many colleague connections are created. Therefore, Microsoft SQL Server is under a heavy load when the daily or the hourly Shared Services Provider (SSP) timer job runs to create colleague connections.
To resolve this issue, apply the following hotfix
package:
983305Â
(http://kbalertz.com/Feedback.aspx?kbNumber=983305/
)
Description of the Office SharePoint Server 2007 hotfix package (Coreserver-x-none.msp): June 29, 2010
Note: After you apply the hotfix that is described in Microsoft Knowledge Base (KB) article 983305, you have to enable a new policy to disable the organization-based colleague auto-population in order to avoid the heavy load on the SSP and temp databases. When this policy is enabled, you can add colleagues manually. However, you cannot find colleagues who are under the same manager if these colleagues are added automatically.
To enable a new policy to disable the organization-based colleague auto-population, you have to use SharePoint Object Model to activate the policy. This is because the new policy does not appear on the Central Administration site.
To activate the new policy, enter code that resembles the following in the SharePoint Object Model to a new Microsoft Visual Studio C# command line project:
using Microsoft.Office.Server;
using Microsoft.Office.Server.UserProfiles;
Â
namespace flipColleaguePolicy
{
   class Program
   {
       static void Main(string[] args)
       {
           try
           {
              If (args.Length<1) {return;}
               ServerContext sctx = ServerContext.GetContext(args[0]);
               UserProfileManager upm = new UserProfileManager(sctx);
               PrivacyPolicyManager mgr = upm.GetPrivacyPolicy();
               foreach (PrivacyPolicyItem pol in mgr.GetAllItems())
               {
                   Console.WriteLine("{0} {1}:{2}", pol.Id, pol.DisplayName, pol.PrivacyPolicy.ToString());
               }
               if (args.Length > 2 && args[1].ToLowerInvariant().Equals("-set"))
               {
                   Guid colleaguepol = new Guid("C2A76725-4C93-4809-9F96-6E5398CDEB56");
                   PrivacyPolicyItem colleaguepolitem = (PrivacyPolicyItem)mgr[colleaguepol];
                   if (args[2].ToLowerInvariant().Equals("dontprocesscolleagues"))
                   {
                       colleaguepolitem.PrivacyPolicy = PrivacyPolicy.Disabled;
                   }
                   else
                   {
                       colleaguepolitem.PrivacyPolicy = PrivacyPolicy.Mandatory;
                   }
                   colleaguepolitem.Commit();
                   Console.WriteLine("Done.");
               }
           }
           catch (Exception ex)
           {
               Console.WriteLine(ex);
           }
Â
       }
   }
}
To disable the organization-based colleague auto-population, use the following command:
flipColleaguePolicy.exe "SharedServiceProviderName" -set dontprocesscolleagues
Note
- Use the following user command to display the current policies and their states:
flipColleaguePolicy.exe "SharedServiceProviderName" - If you want to turn on automatic colleague processing, use the following command:
flipColleaguePolicy.exe "SharedServiceProviderName" -set processcolleagues