crminthefield: Dynamics CRM 2011 DeletionService Async Maintenance Operation Demystified

[Blog bot]

Источник: http://blogs.msdn.com/b/crminthefiel...mystified.aspx
==============

I recently had a customer ask me about the purpose of the DeletionService maintenance operation (AsyncOperationType = 14) executed by the AsyncService in Dynamics CRM 2011.  To provide some context from CRM 4.0, the DeletionService performed physical data cleanup on records that had been logically deleted through the application by setting the DeletionStateCode = ‘2’.  This behavior no longer occurs in CRM 2011 – when records are deleted through the application, they are physically deleted from the database.  So, why the need for a DeletionService maintenance operation?

The database maintenance performed by the DeletionService operation focuses both on organization-wide cleanup and record-specific cleanup.  For the latter cleanup to be performed it’s important to note that during the initial delete action while records are removed from the entity tables, they are also inserted to the dbo.SubscriptionTrackingDeletedObject table.  This table provides the DeletionService with specific ObjectId’s that have been removed so that further, asynchronous cleanup can be performed.

Suppose I have an existing Account:



I then delete the Account through the native application.  Notice, the record is physically deleted from AccountBase, but has now been inserted to SubscriptionTrackingDeletedObject.  The stored procedure ‘p_GetTablesForDeletion’ is called at the beginning of the DeletionService operation to gather up entity types requiring cleanup.



What type of cleanup do you say?  Primarily, Matchcode (duplicate detection) and PrincipalObjectAccess/POA (inherited and shared privileges) records left behind from deleted entity records.

Here are the general steps that the DeletionService performs when executing its maintenance routine:

• Gather up entity tables requiring deletion cleanup by calling p_GetTablesForDeletion stored procedure
• Perform entity specific cleanup for each table returned by joining to the SubscriptionTrackingDeletedObject table
  • Delete associated Matchcode records
  • Delete associated PrincipalObjectAccess (POA) records
• Delete expired client sync subscriptions
• Delete SubscriptionTrackingDeletedObject records
• Delete PostRegarding records based on deleted Posts (activity feeds)

So now you know, the rest of the story…

Austin Jones

Microsoft Premier Field Engineer





Источник: http://blogs.msdn.com/b/crminthefiel...mystified.aspx