Sharepoint 2010 Hotfix for list of issues

Refer http://support.microsoft.com/kb/983497
Following are the list of issues fixed in the hotfix.

• After you move a site to a new content database, the Microsoft SharePoint Foundation 2010 sync does not work on that site.
• If you change your information, a Microsoft SharePoint Server 2010 site still displays your old information after you log on to that site.
• The Welcome Name field is not synced with a user profile as expected if the user obtains access to a site through an Active Directory group. This issue occurs even if the administrator uses the synchronization job to sync profile details for inactive site users.
• If a user profile synchronization service uses a named SQL instance, the service no longer starts after you provision the service. For example, this issue ocurrs when you stop the service.
• You cannot obtain most activity properties from the ActivityManager object without obtaining the LinkList property first.
• When you add a Windows user to SharePoint Server 2010, the user's properties are not populated from Active Directory. Additionally, the user name is the logon name.
• When a SharePoint Server 2010 farm administrator runs the User Profile Change Cleanup job, the performance of the SQL server that hosts the profile database is poor.
• Profile import is slow when a group is deleted. Additionally, the deletion can take hours in some cases. If the group deletion is completed in a transaction, many other database requests are also blocked.
• If all members are removed from a group but the group itself is not deleted, the memberships are not removed.
• When you create a Business Data Catalog (BDC) sync connection, you receive the following error message:
  An error has occurred while accessing the SQL Server database or the SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.
• When you run a BDC import, the import data file is created by running queries on the SharePoint Server 2010 profile store and the BDC back-end store. If an error or exception occurs, all the data is lost.
• If a customer's Lightweight Directory Access Protocol (LDAP) server does not respond within 30 seconds, there is no way for the administrator to create a profile import connection.
• If there are more than 1,000 tag events or rating events during a gatherer run, only the first 1,000 events are processed.
• You clear an activity that you follow in your edit profile screen. However, this action cannot be undone.
• The "people search" result relevance is poor for organization type queries.
• If there are more than 1,000 events during a gatherer run and these events do not fall under certain criteria, only the first 1,000 events are processed correctly. Duplicate events may be generated for the rest of the events.
• When a taxonomy service has a large change log, an offline term store that has never been online cannot recover itself online.
• 2201116 A deadlock occurs in SQL Server when you import many users and groups in Office SharePoint Server 2010

Note To make sure that the hotfix package that is described in KB article 983497 works correctly, you must install the hotfix package that is provided in 2281364 as well.

2281364 Description of the SharePoint Server 2010 hotfix package (wosrv-x-none.msp, pplwfe-x-none.msp, osrv-x-none.msp): July 21, 2010